Transport Resource Management(ERAN 8.1_01)

7/25/2019 Transport Resource Management(ERAN 8.1_01)

http://slidepdf.com/reader/full/transport-resource-managementeran-8101 1/210

eRAN

Transport Resource Management

Feature Parameter Description

Issue 01

Date 2015-03-23

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 thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,

and recommendations in this document are provided "AS IS" without warranties, guarantees or

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 01 (2015-03-23) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/



Contents

1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1

1.2 Intended Audience..........................................................................................................................................................2

1.3 Change History...............................................................................................................................................................2

1.4 Feature Differences by eNodeB Type.............................................................................................................................3

2 Overview......................................................................................................................................... 5

2.1 Introduction.................................................................................................................................................................... 5

2.2 Benefits...........................................................................................................................................................................6

2.3 Architecture.................................................................................................................................................................... 7

2.4 TRM Algorithms............................................................................................................................................................ 8

2.4.1 Transport Resource Configurations and Mapping.......................................................................................................8

2.4.2 Transport Load Control............................................................................................................................................... 8

2.4.3 Transport Congestion Control..................................................................................................................................... 9

3 Transport Resource Configurations and Mapping...............................................................11

3.1 Overview.......................................................................................................................................................................11

3.2 Physical Ports................................................................................................................................................................11

3.3 Transport Resource Groups.......................................................................................................................................... 12

3.3.1 Transport Resource Group Types.............................................................................................................................. 12

3.3.2 Mapping Rules and Applications.............................................................................................................................. 13

3.3.3 Rate Mode Configurations.........................................................................................................................................14

3.4 IP Paths.........................................................................................................................................................................16

3.5 Endpoints......................................................................................................................................................................16

3.6 DiffServ QoS................................................................................................................................................................ 17

3.6.1 QoS Ob jectives..........................................................................................................................................................17

3.6.2 Mapping Between Service Types and DSCPs...........................................................................................................20

4 Transport Load Control..............................................................................................................24

4.1 Overview...................................................................................................................................................................... 24

4.2 Transport Load Calculation.......................................................................................................................................... 24

4.3 Transport Admission Control....................................................................................................................................... 26

4.3.1 Overview................................................................................................................................................................... 26

4.3.2 Admission Control on Transport Resource Groups...................................................................................................26

4.3.3 Admission Control on Physical Ports........................................................................................................................32

eRAN

Transport Resource Management Feature Parameter

Description Contents



ii



4.3.4 Configuration Items...................................................................................................................................................32

4.4 Transport Resource Preemption....................................................................................................................................33

4.4.1 Overview................................................................................................................................................................... 34

4.4.2 Single-Rate-based Preemption Process..................................................................................................................... 34

4.4.3 Dual-Rate-based Preemption Process........................................................................................................................36

4.4.4 Preemption Scenarios and Configuration Items........................................................................................................ 38

4.5 Transport Overbooking.................................................................................................................................................38

4.5.1 Overview................................................................................................................................................................... 39

4.5.2 Transport Resource Group Overbooking...................................................................................................................39

4.5.3 Physical Port Overbooking........................................................................................................................................40

4.6 Transport Load Reporting.............................................................................................................................................41

4.6.1 Overview................................................................................................................................................................... 41

4.6.2 Transport Load Reporting Process............................................................................................................................ 42


4.7 Transport Overload Control..........................................................................................................................................43

4.7.1 Overview................................................................................................................................................................... 43

4.7.2 Transport Overload Control Process..........................................................................................................................44


4.8 Mapping Between Algorithms and MOs......................................................................................................................49

5 Transport Congestion Control.................................................................................................. 50

5.1 Transport Dynamic Flow Control.................................................................................................................................50

5.2 Transport Differentiated Flow Control.........................................................................................................................51

5.2.1 Overview................................................................................................................................................................... 51

5.2.2 Traffic Shaping.......................................................................................................................................................... 52

5.2.3 Queue Scheduling of Transport Resource Groups.................................................................................................... 54

5.2.4 Back-Pressure Algorithm.......................................................................................................................................... 55

5.3 Dynamic Bandwidth Adjustment................................................................................................................................. 57

5.4 IP Performance Monitoring..........................................................................................................................................58

5.5 Mapping Between Algorithms and MOs......................................................................................................................58

6 Application Scenarios.................................................................................................................60

6.1 Different Transport Paths Based on QoS Grade...........................................................................................................61

6.1.1 Overview................................................................................................................................................................... 61

6.1.2 Process of Implementing Different Transport Paths Based on QoS Grade...............................................................61


6.2 User Data Type............................................................................................................................................................. 62

6.3 RAN Sharing................................................................................................................................................................ 63

6.4 Base Station Cascading................................................................................................................................................ 63

7 Related Features...........................................................................................................................64

7.1 Features R elated to LBFD-00300201 DiffServ QoS Support......................................................................................64

7.2 Features R elated to LOFD-00301101 Transport Overbooking.................................................................................... 64

7.3 Features R elated to LOFD-00301102 Transport Differentiated Flow Control.............................................................65

eRAN





iii



7.4 Features Related to LOFD-00301103 Transport Resource Overload Control............................................................. 65

7.5 Features Related to LOFD-00301201 IP Performance Monitoring............................................................................. 65

7.6 Features Related to LOFD-00301202 Transport Dynamic Flow Control....................................................................66

7.7 Features Related to LOFD-003016 Different Transport Paths based on QoS Grade...................................................66

8 Network Impact........................................................................................................................... 67

8.1 LBFD-00300201 DiffServ QoS Support......................................................................................................................67

8.2 LOFD-00301101 Transport Overbooking....................................................................................................................67

8.3 LOFD-00301102 Transport Differentiated Flow Control............................................................................................ 67

8.4 LOFD-00301103 Transport Resource Overload Control............................................................................................. 68

8.5 LOFD-00301201 IP Performance Monitoring............................................................................................................. 68

8.6 LOFD-00301202 Transport Dynamic Flow Control....................................................................................................68

8.7 LOFD-003016 Different Transport Paths based on QoS Grade...................................................................................68

9 Engineering Guidelines............................................................................................................. 699.1 When to Use Transport Resource Management........................................................................................................... 70

9.1.1 Transport Resource Configurations and Mapping.....................................................................................................70

9.1.2 Transport Load Control............................................................................................................................................. 71

9.1.3 Transport Congestion Control................................................................................................................................... 72

9.2 Required Information................................................................................................................................................... 72

9.2.1 Transport Bandwidth Planned by Operators..............................................................................................................72

9.2.2 Transport Resource Mapping.....................................................................................................................................72

9.3 Planning........................................................................................................................................................................73

9.4 Overall Deployment Procedure.................................................................................................................................... 73

9.5 Deployment of Transport Resource Configurations and Mapping...............................................................................73

9.5.1 Process.......................................................................................................................................................................73

9.5.2 Requirements.............................................................................................................................................................73

9.5.3 Data Preparation........................................................................................................................................................ 74

9.5.4 Precautions.................................................................................................................................................................87

9.5.5 Hardware Adjustment................................................................................................................................................88

9.5.6 Initial Configuration.................................................................................................................................................. 88

9.5.7 Activation Observation..............................................................................................................................................93

9.5.8 Reconfiguration......................................................................................................................................................... 99

9.5.9 Deactivation...............................................................................................................................................................999.6 Deployment of Transport Load Control..................................................................................................................... 102

9.6.1 Process.....................................................................................................................................................................102

9.6.2 Requirements...........................................................................................................................................................102

9.6.3 Data Pre paration...................................................................................................................................................... 103

9.6.4 Precautions...............................................................................................................................................................111

9.6.5 Hardwar e Adjustment.............................................................................................................................................. 112

9.6.6 Initial Configuration................................................................................................................................................ 112

9.6.7 Activation Observation............................................................................................................................................ 118

9.6.8 Reconfiguration....................................................................................................................................................... 126

9.6.9 Deactivation.............................................................................................................................................................126

eRAN





iv



9.7 Deployment of Transport Congestion Control........................................................................................................... 128

9.7.1 Process.....................................................................................................................................................................128

9.7.2 Requirements...........................................................................................................................................................128

9.7.3 Data Preparation...................................................................................................................................................... 129

9.7.4 Precautions...............................................................................................................................................................135

9.7.5 Hardware Adjustment..............................................................................................................................................135

9.7.6 Initial Configuration................................................................................................................................................ 135

9.7.7 Activation Observation............................................................................................................................................140

9.7.8 Reconfiguration....................................................................................................................................................... 143

9.7.9 Deactivation.............................................................................................................................................................143

9.8 Performance Monitoring.............................................................................................................................................144

9.9 Parameter Optimization..............................................................................................................................................147

9.10 Troubleshooting........................................................................................................................................................147

9.10.1 Transport Load Control......................................................................................................................................... 147

9.10.2 Transport Congestion Control............................................................................................................................... 148

9.10.3 Alarms................................................................................................................................................................... 149

10 Parameters.................................................................................................................................150

11 Counters.................................................................................................................................... 194

12 Glossary.....................................................................................................................................203

13 Reference Documents.............................................................................................................204

eRAN





v



1 About This Document

1.1 Scope

This document describes resource management for transport, including its technical

principles, related features, network impact, and engineering guidelines. This document

covers the following features:

l LBFD-003002 Basic QoS Management

l LBFD-00300201 DiffServ QoS Support

l LOFD-003011 Enhanced Transmission QoS Management

l

LOFD-00301101 Transport Overbookingl LOFD-00301102 Transport Differentiated Flow Control

l LOFD-00301103 Transport Resource Overload Control

l LOFD-00301202 IP Active Performance Measurement

l LOFD-003016 Different Transport Paths based on QoS Grade

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E

LampSite DBS3900 LampSite

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to

the software release delivered with this document. Any future updates will be described in the

product documentation delivered with future software releases.

This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,

and "eNodeB" refers to LTE FDD eNodeB.

eRAN


Description 1 About This Document



1



1.2 Intended Audience

This document is intended for personnel who:

l Need to understand the features described herein

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:

l Feature change

Changes in features and parameters of a specified version as well as the affected entities.

l Editorial change

Changes in wording or addition of information and any related parameters affected by

editorial changes. Editorial change does not specify the affected entities.

eRAN 8.1 01 (2015-03-23)

This issue does not include any changes.

eRAN8.1 Draft A (2015-01-15)

Compared with 01 (2014-04-26) of eRAN FDD 7.0, Draft A (2015-01-15) of eRAN8.1

includes the following changes.

ChangeType

Change Description ParameterChange

AffectedEntities

Feature

change

Supported the co-IP transmission between

the X2 and eX2 interfaces and modified

the following sections:

4 Transport Load Control

5.2.4 Back-Pressure Algorithm

None Macro

Micro

Editorial

change

Added the impact of the back-pressure

algorithm on the scheduling weight of

transport resource groups in 5.2.4 Back-

Pressure Algorithm.

None -

Revised 9.1.1 Transport Resource

Configurations and Mapping.

None -

eRAN





2



ChangeType

Change Description ParameterChange

AffectedEntities

Revised 9.7.3 Data Preparation. Added the

following

parameters:

RSCGRPAL

G .TXBWAM

IN

RSCGRPAL

G . RXBWAM

IN

-

1.4 Feature Differences by eNodeB Type

Feature Support by Macro/Micro/LampSite eNodeBs

Feature ID Feature Name Supportedby MacroeNodeBs

Supportedby MicroeNodeBs

Supportedby LampSiteeNodeBs

LBFD-003002 Basic QoS

Management

Yes Yes Yes

LBFD-003002

01

DiffServ QoS

Support

Yes Yes Yes

LOFD-003011 Enhanced

Transmission QoS

Management

Yes Yes Yes

LOFD-003011

01

Transport

Overbooking

Yes Yes Yes

LOFD-003011

02

Transport

Differentiated Flow

Control

Yes Yes Yes

LOFD-00301103

Transport ResourceOverload Control

Yes Yes Yes

LOFD-003012

02

IP Active

Performance

Measurement

Yes Yes Yes

LOFD-003016 Different Transport

Paths based on QoS

Grade

Yes No Yes

eRAN





3



Feature Implementation in Macro/Micro/LampSite eNodeBs

Feature Difference

Different Transport

Paths based onQoS Grade

This feature is supported differently by different types of eNodeBs.

l Macro and LampSite eNodeBs support this feature, and the

IPPATHRT MO needs to be configured.

l Micro eNodeBs do not support this feature.

For details about this feature, see 6.1 Different Transport Paths

Based on QoS Grade, 9.3 Planning, 9.5.3 Data Preparation, 9.5.6

Initial Configuration, 9.5.7 Activation Observation, and 9.5.9

Deactivation.

eRAN





4



2 Overview

2.1 Introduction

Transport resources are one type of multiple resources on the radio access network. Transport

resources in LTE mainly include transport bandwidths over S1, X2, and eX2 interfaces, which

are logical interfaces. S1 interfaces consist of S1-C (also known as S1-MME) and S1-U

interfaces. An S1-C interface connects an eNodeB and a mobility management entity (MME)

and transmits control plane information. An S1-U interface connects an eNodeB and a serving

gateway (S-GW), and transmits user plane information. Figure 2-1 shows the logical

architecture of S1/X2 interfaces.

Figure 2-1 Logical architecture of S1, X2, and eX2 interfaces

An X2 interface is set up between two neighboring eNodeBs and has both control-plane and

user-plane information to exchange between the eNodeBs.

An eX2 interface is set up between two eNodeBs to carry coordination data between them

(excluding the coordination data carried on the X2 interface).

TRM manages S1, X2, and eX2 transport bandwidths.

eRAN


Description 2 Overview



5



Table 2-1 provides the QoS requirements by the S1 interface for the transport network.

Table 2-1 QoS requirements by the S1 interface for the transport network

QoS Requirement Optimal Value Recommended Value

Unidirectional delay (ms) 5 10

Unidirectional jitter (ms) 2 4

Packet loss rate 1.0 x 10-6 1.0 x 10-5

Table 2-2 provides the QoS requirements by the X2 interface for the transport network.

Table 2-2 QoS requirements by the X2 interface for the transport network

QoS Requirement Optimal Value Recommended Value

Unidirectional delay (ms) 10 20

Unidirectional jitter (ms) 4 7

Packet loss rate 1.0 x 10-6 1.0 x 10-5

Table 2-3 provides the QoS requirements by the eX2 interface for the transport network.

Table 2-3 QoS requirements by the eX2 interface for the transport network

QoSRequirement

Centralized CloudBB (Ideal Backhaul)

DistributedCloud BB (IdealBackhaul)

Coordination overRelaxed Backhaul

Unidirectional

delay (us)

≤10 ≤130 ≤4000

Packet loss rate 1.0 x 10-3 1.0 x 10-3 1.0 x 10-3

NOTE

l Optimal value: indicates the QoS requirements for supporting all services, including IMS signaling,

video calls, voice calls, and packet data. A better performance is provided when the actual QoS

value of the transport network is closer to the optimal value.

l Recommended value: indicates the QoS requirements for supporting coordination data over the eX2

interface and the packet data services with a QoS class identifier (QCI) of 1, 2, 3, or 7.

2.2 Benefits

Based on the transport resource configurations and mapping, the TRM algorithms implementtransport load control and transport congestion control. Specifically, the TRM algorithms can

eRAN





6



use measures such as admission, preemption, overload control, and flow control to meet QoS

requirements of different services in different transport load scenarios, thereby providing

differentiated services for different users and ensuring user fairness. These measures are taken

based on the physical transport bandwidths of the S1, X2, and eX2 interfaces, bandwidths

configured for different transport resource groups, and IP paths or endpoints mapped from

transport resource groups.

2.3 Architecture

TRM algorithms are categorized into:

l Transport resource configurations and mapping

l Transport load control

l Transport congestion control

TRM algorithms are closely related to radio resource management (RRM) algorithms,

including the uplink radio resource scheduling algorithm and radio interface load balancing

algorithm. The TRM and RRM algorithms use the same control policies.

Figure 2-2 shows the categories of TRM algorithms.

Figure 2-2 Categories of TRM algorithms

eRAN





7



2.4 TRM Algorithms

2.4.1 Transport Resource Configurations and Mapping

Transport resource configurations and mapping are fundamental to TRM. The configurations

and mapping are described as follows:

l Transport resource configurations

Physical ports, transport resource groups, and IP paths or endpoints are configured to

help implement more accurate bandwidth management.

l Mapping between services and transport resources

Services are carried on physical ports and transport resource groups. This mapping is

implemented by mapping service types to differentiated service code points (DSCPs)

based on transmission requirements. This mapping helps determine transmission priorities for transmission differentiation.

2.4.2 Transport Load Control

Transport load control enables the eNodeB to provide differentiated services (DiffServ) to

different users and ensure fair allocation of resources among users when transport resources

are limited. To improve transport bandwidth efficiency and network capacity, transport load

control also enables the eNodeB to control the policies for allocating transport bandwidths

without affecting service quality.

Before performing transport load control, the eNodeB calculates the transport loads involved,

that is, the minimum bandwidth required for the services with specific QoS requirements, based on the actual traffic or reserved bandwidths.

Transport load control consists of the following functions:

l Transport admission control

Transport admission control enables the eNodeB to apply different admission policies to

different types of services to ensure the transmission quality of ongoing services and

increase the admission success rate for high-priority services. The eNodeB supports

transport admission control on transport resource groups and physical ports.

l Transport resource preemption

Transport resource preemption allows higher-priority services to preempt lower-priorityservices. This ensures the access success rate of high-priority services.

l Transport overbooking

Transport overbooking allows the sum of the maximum rates of all admitted services to

exceed the total transport bandwidth, maximizing the number of services admitted.

Transport overbooking supports physical ports and transport resource groups.

l Transport load reporting

When an eNodeB needs to exchange MLB information with other eNodeBs, the

transport layer reports the load status to the radio interface load balancing algorithm,

which then sends the information to other eNodeBs over the X2 interface for load

balancing.

l Transport overload control

eRAN





8



When a network is overloaded, transport overload control releases the resources of low-

priority services to ensure the quality and transmission stability of high-priority services.

2.4.3 Transport Congestion Control

Transport congestion control improves the quality of the transport network when the quality

fluctuates frequently. Transport congestion control involves transport differentiated flow

control and transport dynamic flow control. Table 2-4 describes the usage scenarios for

transport congestion control and algorithms used to implement transport congestion control.

Table 2-4 Usage scenarios for transport congestion control and corresponding algorithms

UsageScenario

Level 1Algorithm

Level 2Algorithm

Description

Congestion on

the interface

boards in aneNodeB

Transport

differentiated flow

control

Traffic shaping Traffic shaping covers

transport resource groups

and physical ports. Byusing traffic shaping, TX

traffic in the uplink is

limited to the configured

bandwidth.

Physical port

scheduling

The ports use Weighted

Round Robin (WRR) for

resource scheduling to

ensure fairness and

differentiation among

weighted transport resource

groups.

Scheduling on

transport resource

groups

Both priority queuing (PQ)

scheduling and non-PQ

scheduling are used for

each queue in a transport

resource group. In non-PQ

scheduling mode, WRR is

used.

Back-pressure Back-pressure

preferentially schedules

non-flow-controllableservices to ensure their

service quality and limits

the rates of non-real-time

services to differentiate

bandwidth allocation

among non-real-time

services.

eRAN





9



UsageScenario

Level 1Algorithm

Level 2Algorithm

Description

Congestion in

the network

outside an

eNodeB

Transport dynamic

flow control

IP PM IP PM monitors end-to-end

network performance to

obtain network quality

information such as traffic

volume, packet loss rate,

and delay variation. IP PM

enhances system

maintainability and

testability and improves

system performance.

Dynamic

bandwidth

adjustment

Dynamic bandwidth

adjustment estimates the

bottleneck bandwidth and

sends the bandwidth

information to the transport

differentiated flow control

algorithm and transport

admission control

algorithm.

Implementing transport dynamic flow control can cause bandwidth change to each transport

resource group, which may lead to congestion in the eNodeB interface boards. Therefore,

transport differentiated flow control must be implemented along with transport dynamic flowcontrol.

eRAN





10



3 Transport Resource Configurations and

Mapping

3.1 Overview

TRM involves configurations of transport resources including physical ports, transport

resource groups, IP paths, and endpoints. TRM aims to provide differentiated services by

implementing configurations and management of transport resources based on service QoS

requirements.

The relationships among the objects to be configured for TRM are as follows:

l A transport resource group can be mapped to only one physical port while a physical port can contain multiple transport resource groups.

l When IP paths are configured, the eNodeB works in link mode. When endpoints are

configured, the eNodeB works in endpoint mode.

– In link mode, an IP path can be configured in only one transport resource group,

while a transport resource group can contain multiple IP paths.

– In endpoint mode, one endpoint group can only be added to one transport resource

group of a physical port; similarly, one peer endpoint can only be added to one

transport resource group of a physical port.

NOTE

For details about link and endpoint modes, see S1/X2 Self-Management Feature Parameter Description and eX2 Self-Management Feature Parameter Description.

3.2 Physical Ports

The physical ports of an eNodeB are the FE/GE, E1/T1, and 10GE ports on the LMPT,

UMPT, and UCCU. For details, see S1/X2 Self-Management Feature Parameter Description

and USU3910-based Multi-BBU Association Feature Parameter Description.

eRAN


Description 3 Transport Resource Configurations and Mapping



11



3.3 Transport Resource Groups

If physical ports are configured, the eNodeB can start working and process services. However,

it may encounter problems in transport bandwidth management in the following situations:

l In a mesh network, a physical port of an eNodeB is connected to multiple nodes such as

a mobility management entity (MME), an S-GW, and another eNodeB. The bandwidths

of these nodes are not shared. To address this problem, the bandwidths are separately

managed for each node.

l When base stations are cascaded, the data of a base station and the data forwarded by

this base station to/from lower-level base stations share the same physical port. To ensure

bandwidth allocation fairness between the two types of data, the bandwidths are

separately managed for each type of data.

l In RAN sharing mode, multiple operators share the bandwidths of an eNodeB. To

achieve dynamic bandwidth sharing and ensure fair allocation of bandwidth among theoperators, the bandwidths are separately managed for each operator.

To meet the requirements in the preceding situations, transport resource groups are configured

for eNodeBs. When transmitted from a service processing board to an interface board, a data

stream first enters a transport resource group and then enters a physical port.

A transport resource group carries a set of data streams, which may include:

l Local data

This type of data involves the control plane, user plane, operation and maintenance

(OM), and IP clock services.

l Passing-by data

This type of data does not differentiate the control plane and user plane.

The eNodeB manages transport bandwidths based on transport resource groups by means of

bandwidth configuration, admission control, and flow control.

3.3.1 Transport Resource Group Types

Traffic shaping, admission control, and flow control can be performed on transport resource

groups.

Transport resource groups are classified into the following types:

l Default transport resource group

Each physical port has a default group. Users do not need to create the default group.

Users can modify the properties of a default transport resource group.

l Dedicated transport resource group

This type of group is created by users. The RSCGRP. PT parameter specifies the number

of a physical port. Each dedicated group corresponds to only one physical port.

Users can set the single-rate mode or dual-rate mode for default and dedicated transport

resource groups. In single-rate mode, users can configure transmit and receive bandwidths by

setting the RSCGRP.TXBW and RSCGRP. RXBW parameters, respectively. In dual-ratemode, users can configure the CIR and PIR, as described in Table 3-1.

eRAN





12



Table 3-1 Dual-rate configuration

Rate Mode Description Parameter

CIR Committed information rate RSCGRP.TXCIR and

RSCGRP. RXCIR

PIR Peak information rate, which is greater than

or equal to the CIR

RSCGRP.TXPIR and

RSCGRP. RXPIR

NOTE

If the default transport resource group is used and the properties of the group are not manually modified,

the group implements scheduling and traffic shaping based on the bandwidth that actually takes effect.

3.3.2 Mapping Rules and ApplicationsAfter being configured, transport resource groups must be mapped to data flows. The

mapping rules are as follows:

l Local user plane data uses either the default or dedicated group.

– If the link mode is required, users can add an IPPATH MO to specify a transport

resource group for local user plane data.

– If the endpoint mode is required, users can run the ADD EP2RSCGRP command

to specify a transport resource group for local user plane data.

l Control plane, OM, IP clock, and passing-by data use the default group if the group type

is not specified. Users can also configure dedicated groups for these data types based on

the destination IP addresses by running the ADD IP2RSCGRP command. In this case,

the dedicated groups implement only traffic shaping but no admission control or flow

control.

The same transport resource group can be allocated to both the S1 interface and the X2

interface.

In cloud BB scenarios, it is recommended that the eX2 interface be mapped to a transport

resource group different than that for the S1/X2 interface. This way, the eNodeB can ensure

the bandwidth allocation fairness between the eX2 and S1/X2 interfaces by scheduling

different transport resource groups. If the eX2 and S1/X2 interfaces share a transport resource

group, data over the eX2 interface will preempt the bandwidth occupied by data over the

S1/X2 interface when the uplink transport bandwidth is limited.

An eNodeB cannot implement flow control on passing-by data in co-transmission scenario. If

local data and passing-by data share a transport resource group, the passing-by data preempts

the bandwidth occupied by the local data when the uplink transport bandwidth is limited.

Therefore, it is recommended that different transport resource groups be specified for local

data and passing-by data. Then, the eNodeB can ensure the bandwidth allocation fairness

between local data and passing-by data by scheduling different transport resource groups.

In RAN sharing mode, the eNodeB implements uplink bandwidth sharing by mapping each

operator to a transport resource group.

The method used for scheduling the transport resource groups of a physical port depends onthe rate mode, as described in Table 3-2.

eRAN





13



Table 3-2 Methods for scheduling the transport resource groups of a physical port

Rate Mode Scheduling WeightSwitch Setting

Scheduling Method

Single-rate mode GTRANSPARA. LPS CHSW is set to

ENABLE(Enable).

WRR is used. The WRR weight of atransport resource group is equal to

the scheduling weight specified by

RSCGRP.WEIGHT for this group.

GTRANSPARA. LPS

CHSW is set to

DISABLE(Disable) .

WRR is used. The WRR weight is

positively correlated with

RSCGRP.TXBW .

Dual-rate mode Not involved The WRR scheduling procedure is

as follows:

l WRR schedules transport

resource groups whose TX CIR is not satisfied. The WRR

weight is positively correlated

with RSCGRP.TXCIR.

l WRR schedules transport

resource groups whose TX CIR

is satisfied. The WRR weight is

equal to the value of

RSCGRP.WEIGHT .

3.3.3 Rate Mode Configurations

The eNodeB supports both single-rate and dual-rate modes. Users can select a rate mode by

setting the GTRANSPARA. RATECFGTYPE parameter. Table 3-3 describes the

configurations of these rate modes.

Table 3-3 Configurations of the rate modes

ConfigurationItem

Single-Rate Mode Dual-rate Mode

Bandwidth mode TX bandwidth specified by

the RSCGRP.TXBW

parameter and RX

bandwidth specified by the

RSCGRP. RXBW

parameter

l TX CIR bandwidth specified by

the RSCGRP.TXCIR parameter

and TX PIR bandwidth specified

by the RSCGRP.TXPIR

parameter

l RX CIR bandwidth specified by

the RSCGRP. RXCIR parameter

and RX PIR bandwidth specified

by the RSCGRP. RXPIR

parameter

eRAN





14



ConfigurationItem

Single-Rate Mode Dual-rate Mode

Configuration

requirement

None l The RSCGRP.TXCIR value of

each transport resource group is

less than or equal to the

RSCGRP.TXPIR parameter.

l The RSCGRP. RXCIR value of

each transport resource group is

less than or equal to the

RSCGRP. RXPIR parameter.

l The sum of the RSCGRP.TXCIR

values of all the transport resource

groups is less than or equal to the

bandwidth of the physical port.

The bandwidth of the physical port

is the smaller value between the

actual rate of the physical port and

the LR .CIR value.

l The sum of the RSCGRP. RXCIR

values of all the transport resource

groups is less than or equal to the


The bandwidth of the physical port

is the smaller value between the

actual rate of the physical port and

the LR . DLCIR value.

Method for

scheduling

transport resource

groups

For details, see Table 3-2. For details, see Table 3-2.

Traffic shaping

method

Traffic shaping is based on

RSCGRP.TXBW .

Traffic shaping is based on

RSCGRP.TXPIR.

Transport load

control method

The sum of the transport

loads of all services using

the same transport resource

group does not exceed the

rate of this group.

l The sum of the transport loads of

all non-flow-controllable services

using the same transport resource

group does not exceed the CIR

bandwidth of this group.

l The sum of the transport loads of

all services using the same

transport resource group does not

exceed the CIR bandwidth of this

group.

If the eNodeB works in dual-rate mode, the dual-rate mode bandwidths can better match

actual bandwidths. To prevent packet loss on the transport network, this mode also ensures

that the total bandwidth used by non-flow-controllable services does not exceed the CIR.

eRAN





15



3.4 IP Paths

If the eNodeB needs to work in link mode, IP paths must be configured to carry local user-

plane data and specific transport resource groups must be allocated for the user-plane data.

IP paths are classified into two types based on whether DSCPs are considered, as described in

Table 3-4.

Table 3-4 IP path

DSCPs Are Considered IP Path Type Description

No ANY This type of IP path is

defined based on the local

IP address

(IPPATH. LOCALIP ) and peer IP address

(IPPATH. PEERIP ) of

packets.

Yes FIXED This type of IP path is

defined based on the local

IP address

(IPPATH. LOCALIP ), peer

IP address

(IPPATH. PEERIP ), and

DSCPs of packets.

The following parameters are used to add an IP path and assign it to a transport resource

group:

l IPPATH. LOCALIP : local IP address

l IPPATH. PEERIP : peer IP address

l IPPATH. PATHTYPE : IP path type, ANY(Any QoS) or FIXED(Fixed QoS)

l IPPATH. DSCP : value of DSCP, which is useful when IPPATH. PATHTYPE is set to

FIXED(FIXED QOS)

l IPPATH. RSCGRPID: ID of the transport resource group to which the IP path isassigned. Note that each IP path can be assigned to only one group. This parameter takes

effect only when the IPPATH. JNRSCGRP parameter is set to ENABLE(Enable).

When the IPPATH. JNRSCGRP parameter is set to DISABLE(Disable), the IP path is

assigned to the default transport resource group.

Any two IP paths cannot have the same combination of IPPATH. LOCALIP ,

IPPATH. PEERIP , and IPPATH. DSCP .

3.5 Endpoints

An endpoint is used to set up a transport link in endpoint mode. The source port of anendpoint is configured in MOs such as SCTPHOST, SCTPPEER , USERPLANEHOST,

eRAN





16



and USERPLANEPEER . Control-plane and user-plane transport links can be automatically

set up at the local end using the destination port information included in a signaling message

and the source port information. For details, see S1/X2 Self-Management Feature Parameter

Description.

3.6 DiffServ QoS

3.6.1 QoS Objectives

Service Quality Requirements

The interface boards of the eNodeB transmit the data for the following services:

l Control plane and user plane services on the S1, X2, and eX2 interfaces

For details, see 3GPP TS 23.401 and eX2 Self-Management Feature Parameter Description.

l Operation and maintenance (OM) services

l IP clock services

l Co-transmission services (bypass data flows)

Table 3-5 describes the quality requirements for these services.

Table 3-5 Service quality requirements

Service Type Quality Requirement Description

User

plane

servi

ces

Real-

time

services

GBR

services

with a QCI

of 1 to 4

The required bandwidths

must be guaranteed.

The packet loss rate must

be controlled and increased

delay due to high buffer

data volumes must be

avoided. If not, service

quality may deteriorate

significantly. For details,

see 3GPP TS 23.401.

Non-flow-

controllable

services in

non-GBR

services,

including

services

with a QCIof 5 by

default

eRAN





17



Service Type Quality Requirement Description

Non-

real-

time

services

Flow-

controllable

services in

non-GBR

services,

including

services

with a QCI

of 6 to 9 by

default

Min_GBR must be

guaranteed.

It is specified by thefollowing parameters:

StandardQci.UlMinGbr ,

ExtendedQci.UlMinGbr ,

StandardQci. DlMinGbr

and

ExtendedQci. DlMinGbr

When the bandwidth

resource is insufficient,

service throughput can be

decreased and data can be

buffered with the basic

quality of non-real-time

services guaranteed.

Control plane services Related data must be

preferentially transmitted.

Traffic volumes are low,

but these services are

closely related to network

KPIs. Therefore, related

data must be preferentially

transmitted and packet loss

must be prevented.

OM

servi

ces

Man-machine language

(MML) services

Related data must be


Traffic volumes are low.

Therefore, the transport

bandwidth must be

preferentially guaranteed.

File Transfer Protocol

(FTP) services

The priority of this service

type is lower than those of

other service types.

Related traffic volumes

fluctuate. The minimum

bandwidth must be

guaranteed.

IP

clock

servi

ces

Clock packets and

related control packets



Traffic volumes are low.

Therefore, the transport

bandwidth must be

preferentially guaranteed.

Passing-by data services The eNodeB schedules passing-by data based on DSCPs.

NOTE

The ExtendedQci.FlowCtrlType parameter can be set for services with extended QCIs. For details

about flow-controllable services with extended QCIs, see section 6.2 User Data Type.

In this document, a user plane service refers to a service carried on an evolved universal

terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB). For details, see

3GPP TS 36.300. The MME informs the eNodeB of the QoS attributes of each user plane

service over the S1 interface. The QoS attributes include: QCI, ARP, GBR, and MBR/UE-

AMBR. MBR stands for maximum bit rate (MBR). UE-AMBR stands for user equipment -

aggregate maximum bit rate.

Capacity Requirements

The capacity requirements are as follows:

eRAN





18



l The system ensures service quality while admitting as many services as necessary, but

does not affect service quality.

l The system prevents congestion while providing as high throughput as necessary for

bursts of non-real-time services by efficiently using bandwidths.

Differentiated Service Requirements

DiffServ is an important technique for ensuring the quality of IP transmissions. TRM provides

different service types with different quality guarantee measures. The eNodeB can select

different types of transport bearers and transmission priorities for different types of services.

Table 3-6 describes the DiffServ requirements for different types of services.

Table 3-6 DiffServ requirements for different types of services

Control Type Service Type DiffServRequirement

ServiceDescription

Flow-controllable

services

Non-real-time

services

When the required

uplink transport

bandwidth exceeds

the total available

bandwidth, the

available bandwidth

must be

preferentially

allocated to non-

flow-controllable

services. The

remaining bandwidth is then

allocated to flow-

controllable services

based on weight

factors.

Traffic volumes

fluctuate

significantly.

OM FTP services These services have

lower priorities than

other services. The

minimum

bandwidths or basic

resources must beguaranteed for these

services.

-

eX2 services The DiffServ

priority of the S1-U

or X2-U is higher

than that of the eX2-

U.

-

eRAN





19



Control Type Service Type DiffServRequirement

ServiceDescription

Non-flow-

controllable services

Real-time services When the required

uplink transport

bandwidths exceed

the total available

bandwidth, the

available bandwidth

must be

preferentially

allocated to real-

time services.

The total traffic

volume fluctuates

insignificantly when

multiple services are

admitted.

Control plane

services


preferentially

transmitted during

network congestion

to ensure low packet

loss rates and short

delays.

-

OM MML services

IP clock services

3.6.2 Mapping Between Service Types and DSCPs

This section describes the following features:

l LBFD-003002 Basic QoS Management

lLBFD-00300201 DiffServ QoS Support

IP-based transmission is implemented over both the S1 and X2 or eX2 interfaces. For IP-

based transmission over the S1 and X2 interfaces, see 3GPP TS 23.401. For IP-based

transmission over the eX2 interface, see eX2 Self-Management Feature Parameter

Description. To ensure the IP transmission quality, the DiffServ technique is introduced. By

using DiffServ, the eNodeB informs each router on a transport path of quality requirements,

which are indicated in the DSCP field in the IP packet header. The DSCP value ranges from 0

to 63. A larger DSCP value indicates a higher scheduling priority for the packet. Figure 3-1

shows the structure of the DSCP field in an Internet Protocol version 4 (IPv4) packet.

Figure 3-1 Structure of the DSCP field in an IPv4 packet

Services are classified and flow control is performed based on the quality requirements for theservices before they are processed in the transport network. In addition, the DSCP field in

eRAN





20



each IP packet is set at the same time. Based on the DSCP field, the QoS mechanism

identifies each type of service and its quality requirements in the network. Also based on the

DSCP field, most of the nodes in the network perform resource allocation, queue scheduling,

and packet discarding, which are collectively called Per Hop Behaviors (PHBs).

To meet the requirements for DiffServ QoS and effectively take advantage of the DiffServfeature of the transport network, the eNodeB sets the DSCP in the DSCP field for each uplink

IP packet transmitted over the S1, X2, or eX2 interface based on the quality requirements for

each service. In the downlink, the evolved packet core (EPC) sets the DSCP fields in IP

packets.

The DiffServ priority policies over the eX2 interface are as follows:

l The eX2-C is carried by SCTP links and has the same priority as the S1-U or X2-C.

l Different eX2-U service types use three different priorities, which correspond to QCI 4,

8, and 9, respectively.

l Large-traffic eX2 services use the priority corresponding to QCI 9 to ensure that the priority of S1-U or X2-U is higher than that of eX2-U.

According to the mapping between service types and DSCPs, the eNodeB implements

different DiffServ priorities for service packets transmitted by the eNodeB interface board.

Table 3-7 lists the default mapping between service types and DSCPs.

Table 3-7 Default mapping between service types and DSCPs

Service Type QCI Resource Type DSCP

S1-U/X2-U 1 GBR 46

2 34

3 34

4 34

5 Non-GBR 46

6 18

7 18

8 18

9 0

eX2-U 4 - 34

8 - 18

9 - 0

S1-C/X2-C/eX2-C

(SCTP)

- - 48

OM (MML) - - 46

OM (FTP) - - 18

eRAN





21



Service Type QCI Resource Type DSCP

IP clock - - 46

NOTE

eX2-U0 carries signaling, eX2-U1 carries high-priority coordination packets, and eX2-U2 carries low-

priority coordination packets. eX2-U0, eX2-U1, and eX2-U2 are taken as QCI4, QCI8, and QCI9

services during scheduling, respectively.

The parameters in the DIFPRI managed object (MO) for mapping service types to DSCPs

include:

l Priority rule (DIFPRI. PRIRULE ): indicates a rule for distinguishing between service

priorities based on applications.

l Signaling priority (DIFPRI. SIGPRI ): indicates the DSCP of packets on the control plane.

l OM MML data priority (DIFPRI.OMHIGHPRI ): indicates the DSCP of OM MML

packets.

l OM FTP data priority (DIFPRI.OMLOWPRI ): indicates the DSCP of OM FTP packets.

l IP clock data priority (DIFPRI. IPCLKPRI ): indicates the DSCP of IP clock packets.

For a user data type, the UDT and UDTPARAGRP MOs must be configured with the

UDT.UDTPARAGRPID and UDTPARAGRP.UDTPARAGRPID parameters set to the same

value. Table 3-8 lists the involved parameters.

Table 3-8 Parameters configured for the transport parameter group of a user data type

MO Configuration Item Parameter ID

UDT Number of the user data type. The values

ranging from 1 to 9 specify standard user

data types and those ranging from 10 to 254

specify extended user data types. Standard

user data types are predefined, whereas

extended user data types must be configured

by running the ADD EXTENDEDQCI

command. The user data types numbered 1to 4 indicate non-flow-controllable services.

UDT.UDTNO

ID of the transport parameter group for a

user data type. The values 40 to 48 are

reserved for standard user data types but not

recommended for extended user data types.

UDT.UDTPARAGRPID

UDTPAR

AGRP

ID of the transport parameter group for a

user data type. The values 40 to 48 are

reserved for standard user data types but not

recommended for extended user data types.

UDTPARAGRP.UDTPARA

GRPID

Priority rule UDTPARAGRP. PRIRULE

eRAN





22



MO Configuration Item Parameter ID

Priority UDTPARAGRP. PRI

Activity factor UDTPARAGRP. ACTFACT

OR

A larger DSCP value indicates a higher priority.

eRAN





23



4 Transport Load Control

4.1 Overview

The eNodeB uses transport load control to determine whether to admit an access request or

release resources that have been allocated for admitted services, based on transport resource

usage. Before performing transport load control, the eNodeB calculates the transport loads

involved, that is, the minimum bandwidth required for the services with specific QoS

requirements, based on the actual traffic or reserved bandwidths.

Transport load control involves the following algorithms:

l Transport admission control

l Transport resource preemption

l Transport overbooking

l Transport load reporting

l Transport overload control

For details about algorithm definitions, see 2.4.2 Transport Load Control. The eNodeB

processes services based on the configured rate mode (single-rate or dual-rate).

4.2 Transport Load Calculation

Transport load calculation enables the eNodeB to calculate the minimum bandwidth requiredfor services with specific QoS requirements based on the actual traffic or reserved

bandwidths. It is the basis of transport admission control, transport resource preemption, and

transport overload control algorithms. Different types of services have different quality

requirements, as described in section 3.6.1 QoS Objectives. The transport load calculation

methods for these services are also different, as described in Table 4-1.

eRAN


Description 4 Transport Load Control



24



Table 4-1 Transport load calculation methods

Service Type TransportLoadCalculation

Method

Description

Real-time

services

Admitted real-time services Transport load =

Actual traffic

volume on the

data link layer

Users can

configure activity

factors for real-

time and non-real-

time services. For

details about

activity factors

and their

configurations,

see section 4.5

TransportOverbooking.

Real-time

services

requiring

admission

QCIs of 1 to 4 Transport load =

GBR x Activity

factor

Non-flow-

controllable

services in non-

GBR services,

including services

with a QCI of 5 by

default

Transport load =

Min_GBR x

Activity factor

Non-real-time services Transport load =

Min_GBR x

Activity factor

User plane, OM MML, and

IP clock services

Transport load = Reserved bandwidth

(RSCGRPALG.TXRSVBW or

RSCGRPALG. RXRSVBW )

If there is no user

plane, OM MML,

or IP clock service, the

recommended

reserved

bandwidth is 0.

Otherwise,

configure the

reserved

bandwidth based

on the actual

traffic volume.

OM FTP services Transport load not calculated OM FTP serviceshave the lowest

priority, with only

the minimum

bandwidth.

Therefore, their

transport loads

are not calculated.

To implement transport admission control, transport loads are calculated for each transport

resource group. The transport load of a group is equal to the total transport load of all theadmitted services in this group. Admitted services consist of real-time, non-real-time, control

eRAN





25



plane, OM, and IP clock services. The uplink and downlink transport loads must be calculated

separately. The transport load of a physical port is equal to the total transport load of all the

transport resource groups configured on this port.

4.3 Transport Admission Control

4.3.1 Overview

Admission control involves radio resources and transport resources. A service can be admitted

only after it has obtained both transport resources and radio resources. Only admission on

transport resources is described in this document.

Transport admission control enables the eNodeB to apply diff erent admission policies to

different types of services to ensure the transmission quality of ongoing services and increase

the admission success rate for high-priority services.

Transport admission control of the eNodeB has the following characteristics:

l The eNodeB performs transport admission control first on transport resource groups and

then on physical ports. Transport admission control is performed separately in the uplink

and downlink.

l A service can be successfully admitted only after both uplink and downlink resources

have been obtained successfully. Different uplink and downlink bandwidths can be

allocated to a service.

l There is an upper limit for GBR services so that non-GBR services can obtain resources.

l Transport admission control is not performed on passing-by data in co-transmission

scenarios.l The transport bandwidths on S1 interfaces are limited. If excessive services are admitted,

service bandwidth requirements cannot be met and service quality will significantly

deteriorate. Therefore, transport admission control must be implemented on S1

interfaces. X2 interfaces are used to transmit handover-related data, which requires low

traffic and a short period. Therefore, transport admission control is not performed on X2

interfaces.

l Transport admission control needs to be performed over the eX2 interface because the

traffic volume over the eX2 interface is high. After the eX2 interface is introduced in

Coordination over Relaxed Backhaul scenarios, the eX2 interface can share physical

ports and transport resource groups with the S1/X2 interface. Such sharing requires high

bandwidth. Therefore, transport admission needs to be performed over the eX2 interface.

4.3.2 Admission Control on Transport Resource Groups

The switch for admission control on transport resource groups can be turned on to ensure

quality of admitted services if transport resources are insufficient. Admission control methods

vary according to the rate mode, as described in Table 4-2. Users can select a rate mode by

setting the GTRANSPARA. RATECFGTYPE parameter.

eRAN





26



Table 4-2 Methods for admission control on transport resource groups

Rate Mode Admission Control Method

Single-rate mode Single-rate-

based admission process.

For details, see section Single-Rate-based Admission

Process.

Dual-rate mode Dual-rate-based

admission process.

For details, see section Dual-Rate-based Admission

Process.

Single-Rate-based Admission Process

Figure 4-1 shows the single-rate-based admission process for the admission of a new service.

Figure 4-1 Single-rate-based admission process

eRAN





27



The single-rate-based admission process is as follows:

1. The eNodeB determines the admission threshold based on the type of service as follows.

If... Then...

The service is a handover, RRC

connection reestablishment, or

emergency service

The admission threshold is set to the

threshold configured for handover services.

The service is an eX2 service For the default transport resource group, the

admission threshold is set to 70%.

For a dedicated transport resource group, the

admission threshold is set to the OLC clear

threshold.

The service is a service of other types. The admission threshold is set to the

threshold configured for the gold, silver, or bronze service corresponding to the service

type. For the admission threshold for each

type of service, see section 4.3.4

Configuration Items.

2. The eNodeB selects available transport resource groups for the service. When a new

service requests admission, the MME informs the eNodeB of the S-GW IP address and

service QCI. Upon receiving the information, the eNodeB obtains the DSCP used by the

service by querying the mapping between QCIs and DSCPs, and then determines the

available groups based on the S-GW IP address and DSCP.

3. The eNodeB calculates transport loads, and then admits or rejects the service based on

the available groups. For details about transport load calculation methods, see Table 4-1.

In single-rate mode, the eNodeB calculates the transport loads based on the single-rate

admission bandwidths of transport resource groups. For details about the definitions of the

single-rate admission bandwidths, see Table 4-7.

In single-rate mode, GBR services take precedence over non-GBR services, without using up

all resources. The eNodeB processes non-GBR services after it has processed all GBR

services.

If... Then...

The service

is a GBR

service

The eNodeB first admits the service based on the GBR service admission

threshold if the following condition is met:

[(Sum of the transport loads of the GBR services admitted to the transport

resource group + Transport load of the new service)/Single-rate admission

bandwidth of the transport resource group] < GBR service admission

threshold

Then the eNodeB admits the service based on the corresponding admission

threshold (see Table 4-4) if the following condition is met:

[(Sum of the transport loads of all the services admitted to the transport


bandwidth of the transport resource group] < Service admission threshold

eRAN





28



If... Then...

The service

is a non-

GBR service

If the default activity factor 0 is reserved for non-GBR services, indicating

that no bandwidth needs to be reserved, the eNodeB can admit the non-

GBR services directly.

The eNodeB admits other services based on the corresponding admission

threshold (see Table 4-4) if the following condition is met:

[(Sum of the transport loads of all the services admitted to the transport


bandwidth of the transport resource group] < Service admission threshold

Dual-Rate-based Admission Process

Figure 4-2 shows the dual-rate-based admission process for the admission of a new service,

which is applicable to the uplink and downlink.

eRAN





29



Figure 4-2 Dual-rate-based admission process

The dual-rate-based admission process is as follows:

1. The eNodeB determines the admission threshold based on the type of service. For the

admission threshold for each type of service, see section 4.3.4 Configuration Items.

2. The eNodeB selects available transport resource groups for the service. When a newservice requests admission, the MME informs the eNodeB of the S-GW IP address and

eRAN





30



service QCI. Upon receiving the information, the eNodeB obtains the DSCP used by the

service by querying the mapping between QCIs and DSCPs, and then determines the

available groups based on the S-GW IP address and DSCP.

3. The eNodeB calculates the transport loads, and then admits or rejects the service based

on the available transport resource groups. For details about transport load calculationmethods, see Table 4-1.

l The eNodeB decides whether the service is a non-flow-controllable service.

If... Then...

The service is a

non-flow-

controllable

service

l The eNodeB first admits the service based on the CIR admission

bandwidth if the following condition is met:

[(Sum of the transport loads of the non-flow-controllable services

admitted to the transport resource group + Transport load of the

new service)/CIR admission bandwidth of the transport resource

group] < Service admission threshold

l Then the eNodeB admits the service based on the PIR admission bandwidth if the following condition is met:

[(Sum of the transport loads admitted to the transport resource

group + Transport load of the new service)/PIR admission

bandwidth of the transport resource group] < Service admission

threshold

The service is a

flow-controllable

service

The eNodeB admits a non-eX2 service based on the PIR admission

bandwidth if the following condition is met: The eNodeB admits an

eX2 service based on the PIR admission bandwidth and the following

admission thresholds:

For the default transport resource group, the admission threshold is set

to 70%. For a dedicated transport resource group, the admissionthreshold is set to the OLC clear threshold.

NOTE

The eNodeB admits only non-flow-controllable services based on the CIR admission bandwidth. Non-

flow-controllable services may experience packet loss if the available bandwidth is lower than the CIR

admission bandwidth. Therefore, the bandwidth for non-flow-controllable services must be lower than

the CIR admission bandwidth.

l The eNodeB decides whether the service is a GBR service.

If... Then...

The service is

a GBR

service

The eNodeB admits the service based on the admission threshold for GBR

services if the following condition is met:

[(Sum of the transport loads of the GBR services admitted to the transport

resource group + Transport load of the new service)/PIR admission

bandwidth of the transport resource group] < GBR service admission

threshold

The service is

a non-GBR

service

The eNodeB admits the service directly.

eRAN





31



4.3.3 Admission Control on Physical Ports

Users can turn on the admission control switch of a physical port during physical port

overbooking. This prevents the total transport load on all the transport resource groups from

exceeding the bandwidth capacity of the physical port.

The admission control process on a physical port is as follows:

1. The eNodeB calculates the transport loads on the physical port, as described in Table

4-3.

Table 4-3 Calculation of the transport loads on the physical port

Configuration Item Transport Load Calculation

Physical port The transport load is calculated as the sum of the transport

loads on all the transport resource groups configured on

the physical port.

Transport resource group The transport load is calculated as the sum of the transport

loads of the non-flow-controllable services, the transport

loads of the flow-controllable services, and the reserved

bandwidth of the transport resource group.

NOTE

In cascading scenarios, the transport load on the transport resource group configured for the data

flows of lower-level eNodeBs can be determined by the fixed bandwidth reserved for this group.2. The eNodeB determines the uplink or downlink admission bandwidth of the physical

port.

If... Then...

The limited rate (LR)

bandwidth is configured

for the physical port

The admission bandwidth of the physical port is the

smaller value between the LR bandwidth and actual


NOTE

The LR bandwidth can be the LR .CIR bandwidth (in the uplink)

or LR . DLCIR bandwidth (in the downlink).

The LR bandwidth is notconfigured for the

physical port

The admission bandwidth of the physical port is the actual bandwidth of the physical port.

3. The eNodeB performs admission control on transport resource groups first and then on

physical ports. Admission control on physical ports is the same as that on transport

resource groups in the single-rate-based admission process.

4.3.4 Configuration Items

To ensure higher admission success rate of high-priority services, the admission threshold for high-priority services must be higher than or equal to that for common services.

eRAN





32



Table 4-4 lists the configuration items for transport admission control, which is performed by

the eNodeB.

Table 4-4 Configuration items for transport admission control

ConfigurationItem

Uplink Parameter Downlink Parameter

Admission control

switch of a transport

resource group

TACALG. RSCGRPULCACSW

ITCH

TACALG. RSCGRPDLCACSW

ITCH

Admission control

switch of a physical

port

TACALG. PORTULCACSW TACALG. PORTDLCACSW

Admission

threshold for handover services

TACALG.TRMULHOCACTH TACALG.TRMDLHOCACTH

Admission

threshold for new

gold-type services

TACALG.TRMULGOLDCAC

TH

TACALG.TRMDLGOLDCAC

TH

Admission

threshold for new

silver-type services

TACALG.TRMULSILVERCA

CTH

TACALG.TRMDLSILVERCA

CTH

Admission

threshold for new

bronze-typeservices

TACALG.TRMULBRONZEC

ACTH

TACALG.TRMDLBRONZEC

ACTH

Admission

threshold for GBR

services

TACALG.TRMULGBRCACT

H

TACALG.TRMDLGBRCACT

H

Admission control

switch of

emergency services

TACALG. EMCTACPSW TACALG. EMCTACPSW

OLC clear threshold TOLCALG.TRMULOLCREL

TH

TOLCALG.TRMDLOLCREL

TH

NOTE

When the switch is turned on, emergency services are admitted successfully without any restrictions.

When the switch is turned off, emergency services are admitted if the bandwidth congestion rate is less

than the admission thresholds for handover services, as listed in Table 4-4.

4.4 Transport Resource Preemption

eRAN





33



4.4.1 Overview

This document describes only transport resource preemption. For details about radio resource

preemption, see Admission and Congestion Control Feature Parameter Description.

After the preemption relationships between services and between UEs are configured, a newservice that is initially rejected can preempt lower-priority services. The ARP IE of a service

includes the following fields:

l Priority Level: indicates the priority of this service.

l Preemption Capability: indicates whether this service can preempt transport resources

from other services.

l Preemption Vulnerability: indicates whether transport resources for this service can be

preempted.

When the TACALG.TRMULPRESW or TACALG.TRMDLPRESW parameter is set to

ON(On), if a new service fails in transport admission and the preemption capability field in

the ARP specified that the service can be preempted, it preempts resources from other

services that are in the same transport resource group as itself. The eNodeB performs uplink

and downlink resource preemption separately but in the same manner.

Transport resource preemption processes vary according to the rate mode, as described in

Table 4-5.

Table 4-5 Transport resource preemption processes

Rate Mode Preemption Process

Single-rate mode Single-rate-based preemption process. For details, see section

4.4.2 Single-Rate-based Preemption Process.

Dual-rate mode Dual-rate-based preemption process. For details, see section

4.4.3 Dual-Rate-based Preemption Process.

4.4.2 Single-Rate-based Preemption Process

If a new service fails to be initially admitted and it can preempt other services (which is

indicated by the preemption capability field), it performs a single-rate-based preemption, as

shown in Figure 4-3.

eRAN





34



Figure 4-3 Single-rate-based preemption process

The single-rate-based preemption process is as follows:

1. The eNodeB determines the services to be preempted as follows.

If... Then...

The admission fails because the

resource usage of GBR services has

reached the upper limit

The new service attempts to preempt the

preemptable resources used by GBR

services.

The admission fails because of other

reasons


resources used by all other preemptable

services in this group.

2. The eNodeB sorts the preemptable services.

eRAN





35



Emergency services can preempt all non-emergency services, including the services with

the Pre-emption Vulnerability field in the ARP information element (IE) set to "not pre-

emptable."

The services to be sorted according to integrated priorities must meet all the following

conditions:– The services can be preempted, which is indicated by the value "pre-emptable" of

the Pre-emption Vulnerability field in the ARP IE.

– The services have lower ARP priorities than the new service.

– The activity factors for the non-emergency services are not set to 0.

Integrated priorities are determined based on ARP priorities and transport loads:

– ARP priorities are first compared. A smaller value of the ARP Priority Level IE in

the ARP field of the service indicates a higher integrated priority and a higher

probability of preempting other service resources.

– Transmission loads are then compared. A service with a higher transport load

indicates a lower integrated priority and a higher probability that the resourcesoccupied by this service are preempted.

3. The new service preempts the resources.

The services that can be preempted are preempted in ascending order by integrated

priority until the total transport load of all the preempted services is greater than or equal

to that of the new service.

4.4.3 Dual-Rate-based Preemption Process

If a new service fails to be initially admitted but it can preempt resources of other services, or

the new service is an emergency service, the dual-rate-based preemption process is

performed, as shown in Figure 4-4. The value "pre-emptable" of the preemption capabilityfield in the ARP IE indicates that the service can preempt transport resources.

eRAN





36



Figure 4-4 Dual-rate-based preemption process

The dual-rate-based preemption process is as follows:

1. The eNodeB determines the services to be preempted as follows.

If... Then...

The admission fails because the resource

usage of GBR services has reached the

upper limit


preemptable resources used by GBR

services.

eRAN





37



If... Then...

The admission fails because the transport

load of non-flow-controllable services

reaches the CIR admission bandwidth of

the transport resource group


preemptable resources used by non-flow-

controllable services.

The admission fails because of other

reasons


preemptable resources used by all other

services.

2. The eNodeB sorts the preemptable services.

The sorting rules are the same as those in the single-rate-based preemption process. For

details, see step 2 in section 4.4.2 Single-Rate-based Preemption Process.

3. The new service preempts the resources.

The preemption methods are the same as those in the single-rate-based preemption

process. For details, see step 3 in section 4.4.2 Single-Rate-based Preemption Process.

4.4.4 Preemption Scenarios and Configuration Items

The preemption scenarios are described as follows:

l If the switch is turned off, after an emergency service fails to be admitted to a transport

resource group or physical port, transport resource preemption is triggered regardless of

whether the preemption switch is turned on. All non-emergency services can be

preempted, including those with the Pre-emption Vulnerability field in the ARP IE set to

"not pre-emptable."l Emergency services cannot be preempted.

l If the UDTPARAGRP. ACTFACTOR parameter is set to 0 for a service, admission

control is not performed on the service and the service cannot be preempted.

NOTE

For details about emergency services, see Emergency Call Feature Parameter Description.

Inter-service and inter-UE preemption are configurable. Table 4-6 lists the configuration

items and related parameters.

Table 4-6 Configuration items for transport resource preemption

Configuration Item Uplink Parameter Downlink Parameter

Preemption algorithm

switch

TACALG.TRMULPRESW TACALG.TRMDLPRESW

Activity factor for a user

data type

UDTPARAGRP. ACTFACTOR

4.5 Transport Overbooking

eRAN





38



4.5.1 Overview

This section describes the feature LOFD-00301101 Transport Overbooking.

Acting as the gain of the transport admission control algorithm, transport overbooking allows

the sum of the maximum rates of all admitted services to exceed the total transport bandwidth.

In this way, It can admit as many services as necessary.

The transport bandwidth on the S1 interface is limited. Therefore, transport overbooking is

used to improve service quality and enlarge system capacity. This achieves high statistical

multiplexing gains and resource usage.

In comparison, neither transport admission control nor transport overbooking is required on

the X2 interface because this interface processes only handovers, which involve low traffic

volumes and last for short periods.

Transport overbooking of eNodeBs is classified into transport resource group overbooking

and physical port overbooking. The former implements statistical multiplexing of transportresource group bandwidths based on activity factors. The latter implements statistical

multiplexing of physical port bandwidths based on the admission bandwidths configured for

the transport resource groups according to the rate mode.

4.5.2 Transport Resource Group Overbooking

The eNodeB implements transport admission control on each transport resource group. To

implement transport resource group overbooking, Huawei eNodeBs reserve bandwidths for

services based on the minimum reserved bandwidth resources (but not based on the MBR or

AMBR) during admission control. The eNodeB reserves bandwidths for real-time and non-

real-time services as follows:

l For real-time services that request access to the network, the eNodeB reserves

bandwidths based on the product of the GBR (or Min_GBR) value and the activity

factor.

l For ongoing real-time services, the eNodeB reserves bandwidths based on the actual

traffic volume.

l For non-real-time services that request admission or are already admitted, the eNodeB

reserves bandwidths based on the product of the Min_GBR value and the activity factor.

The effect of transport resource group overbooking can be adjusted based on activity factors.

The activity factor for a type of service equals the ratio of the active duration to the total

online duration. During transport admission, a smaller activity factor indicates a lower reserved bandwidth for services and higher overbooking gains. It also indicates a higher

probability that too many services are admitted and a lower probability that the quality of

services is ensured.

Bandwidths are reserved for real-time services based on their actual traffic volumes, which

are usually stable but sometimes vary. Variations may cause a transport overload. Therefore,

transport overload control is required. For details, see section 4.7 Transport Overload

Control.

Traffic volumes of non-real-time services vary significantly, and TX rates may far exceed the

Min_GBR value, which may cause congestion in the transport resource groups. Therefore,

transport differentiated flow control is required to ensure fairness and differentiation amongnon-real-time services. For details, see section 5.2 Transport Differentiated Flow Control.

eRAN





39



4.5.3 Physical Port Overbooking

Multiple transport resource groups can be configured on each port of an eNodeB board. To

implement physical port overbooking, WRR scheduling is used among transport resource

groups on the LMPT, UMTP, and UMDU. For details about the scheduling weight of eachtransport resource group, see Table 3-2.

In addition, the sum of the admission bandwidths of all transport resource groups can be

greater than the bandwidth of the physical port. To enable physical port overbooking, users

can set the uplink or downlink overbooking switch for the physical port

(TACALG. PORTULOBSW or TACALG. PORTDLOBSW , respectively) to ON(On).

The initial admission bandwidth for transport resource groups varies according to the

configured rate mode, as described in Table 4-7.

Table 4-7 Initial admission bandwidth for transport resource groups

Rate Mode Initial Admission Bandwidths of Transport ResourceGroups

Single-rate mode The uplink admission bandwidth is RSCGRP.TXBW , and the

downlink admission bandwidth is RSCGRP. RXBW .

Dual-rate mode l The uplink and downlink CIR admission bandwidths of a

transport resource group are specified by

RSCGRP.TXCIR and RSCGRP. RXCIR, respectively.

l The uplink and downlink PIR admission bandwidths of a

transport resource group are specified by

RSCGRP.TXPIR and RSCGRP. RXPIR, respectively.

The uplink/downlink admission bandwidth of a transport resource group is adjusted as

follows:

l If the dynamic TX or RX bandwidth adjustment switch (RSCGRPALG.TXBWASW or

RSCGRPALG. RXBWASW ) is turned on, the following adjustments are made:

– If the single-rate mode is used, the admission bandwidth is adjusted according to

the congestion status of the transport network to ensure that the admission

bandwidth does not exceed the bottleneck bandwidth of the network.

–

If the dual-rate mode is used, the CIR admission bandwidth is not adjusted. The PIR admission bandwidth is adjusted according to the congestion status of the transport

network to ensure that the PIR admission bandwidth does not exceed the bottleneck

bandwidth of the network. The minimum PIR admission bandwidth must be equal

to or greater than the CIR admission bandwidth.

l If the uplink or downlink overbooking switch of the physical port

(TACALG. PORTULOBSW or TACALG. PORTDLOBSW , respectively) is set to

OFF(Off), the admission bandwidth is adjusted according to Table 4-8.

eRAN





40



Table 4-8 Admission bandwidth adjustment methods for transport resource groups

Rate Mode Criterion Adjustment Method

Single-rate mode The sum of the configured

bandwidths of all transportresource groups exceeds

the bandwidth of the

physical port.

The admission bandwidths of

transport resource groups areadjusted based on their actual

scheduling weights to ensure that

the total admission bandwidth does

not exceed the bandwidth of the

physical port.

Dual-rate mode The sum of the configured

PIR bandwidths of all


exceeds the bandwidth of

the physical port.

The PIR admission bandwidths of

transport resource groups are

adjusted based on their actual

scheduling weights to ensure that

the total PIR admission bandwidth

does not exceed the bandwidth of the physical port.

The sum of the configured

CIR bandwidths of all


exceeds the bandwidth of

the physical port.

The CIR admission bandwidths of

transport resource groups are

adjusted to ensure that the total CIR

admission bandwidth does not

exceed the bandwidth of the

physical port.

In addition, each adjusted CIR

admission bandwidth must have a

positive correlation with the

corresponding configured CIR bandwidth.

If the sum of the configured bandwidths of all transport resource groups is far beyond the

bandwidth of a physical port, the overbooking gain is high but the probability that the desired

service bandwidth is allocated is low. The configured bandwidth of a group is

RSCGRP.TXBW or RSCGRP. RXBW in single-rate mode; it is RSCGRP.TXPIR or

RSCGRP. RXPIR in dual-rate mode.

4.6 Transport Load Reporting

4.6.1 Overview

When the load status information of an eNodeB needs to be sent to another eNodeB, the

transport layer reports the information to the radio interface load balancing algorithm. Then,

the information is sent to the other eNodeB over the X2 interface for load balancing.

After the transport load status is initialized, the transport load status is checked and an

associated message is sent to the radio interface load balancing algorithm at regular intervals.

NOTE

For details about the load balancing algorithm, see Mobility Load Balancing Feature Parameter Description.

eRAN





41



4.6.2 Transport Load Reporting Process

The transport load reporting process is closely related to the load control process.

Figure 4-5 shows the load control process. The middle status indicates the transitional stage

between two states. For example, the transport load in the Middle Status is reported as low before it transits to the HighLoad state from the MediumLoad state, that is, before it reaches

the HighLoad trigger threshold. Similarly, the transport load in the Middle Status is reported

as high before it transits to the MediumLoad state from the HighLoad state, that is, before it

reaches the HighLoad clearance threshold.

Figure 4-5 Load control process


Users can enable the eNodeB to enter a different transport load status by setting the

parameters listed in Table 4-9.

eRAN





42



Table 4-9 Configuration items of the transport load status

Configuration Item Parameter Load Status

HighLoad Trigger

threshold

TLDRALG.TRMULLDR

TRGTH (uplink)TLDRALG.TRMDLLDR

TRGTH (downlink)

In the uplink/downlink, if the

ratio of the transport load to thetransport bandwidth exceeds the

corresponding threshold for a

specified period, the transport

load enters the HighLoad state.

Clearance

threshold

TLDRALG.TRMULLDR

CLRTH (uplink)

TLDRALG.TRMDLLDR

CLRTH (downlink)


ratio of the transport load to the

transport bandwidth falls below

the corresponding threshold for a


load enters the MediumLoad

state.

MediumLo

ad

Trigger

threshold

TLDRALG.TRMULML

DTRGTH (uplink)

TLDRALG.TRMDLML

DTRGTH (downlink)



transport bandwidth exceeds the

corresponding threshold for a


load enters the MediumLoad

state.

Clearance

threshold

TLDRALG.TRMULML

DCLRTH (uplink)

TLDRALG.TRMDLML

DCLRTH (downlink)



transport bandwidth falls below

the corresponding threshold for aspecified period, the transport

load enters the LowLoad state.

4.7 Transport Overload Control

4.7.1 Overview

This section describes the feature LOFD-00301103 Transport Resource Overload Control.

Transport resource overload is a situation where the bandwidths reserved for ongoing services

are not guaranteed because of excessive transport loads. During transport OLC, the eNodeB

periodically checks whether transport resources are overloaded. If transport resources are

overloaded, the eNodeB releases the services that can be preempted and have low priorities to

ensure the quality of the high-priority services.

Transport overload may occur on the S1 interface in the following situations:

l The transport load of real-time services is defined as the actual traffic. As a result, any

fluctuations in actual traffic result in changes in the transport load.

l The admission bandwidths of transport resource groups change along with the transport

network, which results in changes in the transport load. For details, see section 5.1Transport Dynamic Flow Control.

eRAN





43



Transport overload control is not performed over the X2 interface.

Transport overload control can be performed over the eX2 interface. In Coordination over

Relaxed Backhaul scenarios, if transport bandwidth changes and transport overload occurs,

the eNodeB preferentially releases eX2 services.

4.7.2 Transport Overload Control Process

Transport OLC involves transport load check and OLC action. The eNodeB periodically

checks the uplink and downlink transport loads on each transport resource group in the same

manner. Figure 4-6 shows the transport load check mechanism.

Figure 4-6 Transport load check mechanism

OLC methods vary according to the rate mode, as described in Table 4-10. Users can select a

rate mode by setting the GTRANSPARA. RATECFGTYPE parameter.

Table 4-10 OLC methods for transport resource groups

Rate Mode OLC Method

Single-rate mode Single-rate-based

OLC.

For details, see section Single-Rate-based

OLC Process

Dual-rate mode Dual-rate-based OLC. For details, see section Dual-Rate-based OLC

Process

Single-Rate-based OLC Process

Figure 4-7 shows the single-rate-based PLC process.

eRAN





44



Figure 4-7 Single-rate-based OLC process

1. The single-rate-based OLC process is as follows: The eNodeB calculates the transport

load ratio of each transport resource group using the following formula: Transport load

ratio = Transport load/Admission bandwidth

For details about the calculation methods of transport loads and admission bandwidths,

see section 4.2 Transport Load Calculation

2. The eNodeB compares the transport load ratio with the OLC thresholds and determines

whether to perform OLC.

a. If the transport load ratio is higher than the OLC trigger threshold specified by the

TOLCALG.TRMULOLCTRIGTH parameter and the state lasts for a specified

period (OLC trigger interval), the transport resource group is in the overload state.

In this case, the eNodeB activates OLC. The eNodeB sorts all the non-emergency

services whose activity factors are not 0 in the transport resource group in

ascending order of priority according to the service release rules in Table 4-11.

Then, it periodically releases the resources for these services in sequence until the

quantity defined by the TOLCALG.TRMOLCRELBEARERNUM parameter isreached.

eRAN





45



b. If the transport load ratio is lower than the OLC clear threshold specified by the

TOLCALG.TRMULOLCRELTH parameter and the state lasts for a specified

period (OLC trigger interval), the transport resource group is in the non-overload

state. The eNodeB deactivates OLC.

c. If the transport load ratio is not higher than the OLC trigger threshold or the statedoes not last for the OLC trigger interval, the eNodeB does not activate OLC.

Table 4-11 Service release rules

ComparisonSequence

Comparison Item Service Release Rule

1 pre-emptionVulnerability field Only preemptable services are

released.

2 priorityLevel field A service with a smaller priorityLevelvalue has a higher priority, indicating

a lower probability of being released.

3 Transport load A service with a smaller transport

load value has a higher priority,

indicating a lower probability of

being released. For details about the

transport load calculation, see section

4.2 Transport Load Calculation.

NOTE

To ensure that the S1/X2 interface takes priority over the eX2 interface, eX2 services are preferentially

released if the eX2 and S1 interfaces share transport resources and transport overload occurs.

Dual-Rate-based OLC Process

Figure 4-8 shows the dual-rate-based OLC process.

eRAN





46



Figure 4-8 Dual-rate-based OLC process

1. The dual-rate-based OLC process is as follows: The eNodeB calculates the transport load

ratios of each transport resource group using the following formulas:

–CIR transport load ratio = Transport load of non-flow-controllable services/CIR admission bandwidth

– PIR transport load ratio = Transport load/PIR admission bandwidth

For details about the calculation methods of transport loads and admission bandwidths,

see 4.2 Transport Load Calculation.

2. The eNodeB compares the transport load ratio with the OLC thresholds and determines

whether to perform OLC.

– If the transport load ratio is higher than the OLC trigger threshold and the state lasts

for a specified period (OLC trigger interval), the transport resource group is in the

overload state. In this case, the eNodeB performs an OLC action according to the

following table. where:

eRAN





47



If... Then...

The CIR transport load

ratio is higher than the

OLC trigger threshold

The transport resource group enters the CIR overload

state. The eNodeB sorts all non-flow-controllable services

excluding emergency services and services with the

activity factor of 0 in the transport resource group in

ascending order of priority according to the service

release rules in Table 4-11. Then, it periodically releases

the resources for these services in sequence until the

quantity defined by the

TOLCALG.TRMOLCRELBEARERNUM parameter is

reached.

The PIR transport load

ratio is higher than the

OLC trigger threshold

The transport resource group enters the PIR overload

state. The eNodeB sorts all services excluding emergency

services and services with the activity factor of 0 in the

transport resource group in ascending order of priority

according to the service release rules in Table 4-11. Then,

it periodically releases the resources for these services in

sequence until the quantity defined by the

TOLCALG.TRMOLCRELBEARERNUM parameter is

reached.

– If the transport load ratio is lower than the OLC clear threshold and the state lasts

for a specified period (OLC trigger interval), the transport resource group is in the

non-overload state with CIR and PIR differentiated, and the eNodeB deactivates

OLC.– If the transport load ratio is not higher than the OLC trigger threshold or the state

does not last for the OLC trigger interval, the eNodeB does not activate OLC.


The eNodeB performs OLC for each transport resource group. Table 4-12 lists the main OLC

configuration items.

Table 4-12 Main OLC configuration items

Configuration Item Parameter

OLC switch TOLCALG.TRMULOLCS

WITCH (uplink)

TOLCALG.TRMDLOLCS

WITCH (downlink)

OLC trigger threshold TOLCALG.TRMULOLCT

RIGTH (uplink)

TOLCALG.TRMDLOLCT

RIGTH (downlink)

OLC clear threshold TOLCALG.TRMULOLCR

ELTH (uplink)

TOLCALG.TRMDLOLCR

ELTH (downlink)

Number of bearers that can

be released during an OLC

session

TOLCALG.TRMOLCRELBEARERNUM

eRAN





48



4.8 Mapping Between Algorithms and MOs

Table 4-13 lists the mapping between transport load control algorithms and MOs.

Table 4-13 Mapping between transport load control algorithms and MOs

Algorithm MO

Transport admission control TACALG

Transport resource preemption TACALG

Transport overbooking UDTPARAGRP for transport overbooking

on transport resource groups

TACALG, RSCGRP, and LR for transport

overbooking on physical ports

Transport load reporting TLDRALG

Transport resource overload control TOLCALG

eRAN





49



5 Transport Congestion Control

5.1 Transport Dynamic Flow Control

This section describes the feature LOFD-00301202 Transport Dynamic Flow Control.

The transport bandwidth of the S1/X2/eX2 interface changes dynamically in the following

scenarios:

l When transmission media such as the x Digital Subscriber Line (xDSL) and microwave

are used, the bandwidth of the transport layer may change dynamically.

l When multiple eNodeBs share the system bandwidth in the scenario of eNodeB

cascading or network convergence, the available bandwidth of each eNodeB

dynamically changes.

l When an eNodeB is connected to multiple S-GWs in an S-GW service area, the actual

bandwidth between the eNodeB and each S-GW changes dynamically. For details about

S-GW service areas, see 3GPP TS 23.401.

In the preceding scenarios, the available bottleneck bandwidth may be lower than the TX

bandwidth configured for transport resource groups. If admission control and flow control are

performed based on the configured TX bandwidth, network congestion may occur and lead to

the following results:

l Excessive services are admitted, and there may not be enough bandwidths available for

services.

l Fairness and differentiation of non-real-time services are not guaranteed.

To address these problems, transport dynamic flow control estimates the bottleneck

bandwidth of the transport network based on the transmission quality information provided by

IP PM. It dynamically adjusts the TX rates of transport resource groups on eNodeB interface

boards to limit the rates within the bottleneck bandwidth. Transport dynamic flow control

aims to prevent network congestion and ensure the transmission quality of services when the

transport bandwidth dynamically changes. Figure 5-1 shows the IP PM process.

eRAN


Description 5 Transport Congestion Control



50



Figure 5-1 IP PM process

Transport dynamic flow control is implemented by the eNodeB for each transport resource

group. This function involves IP PM, transport differentiated flow control, and dynamic

bandwidth adjustment. The transport dynamic flow control process is as follows:

1. The eNodeB performs periodic forward monitoring (FM).

2. The S-GW responds with a Backward Report (BR) packet after receiving an FM packet.

3. The eNodeB calculates the delay variation and packet loss rate after receiving the BR

packet.

4. The eNodeB performs bandwidth adjustment for each transport resource group based on

the average delay variation and packet loss rate during each statistical period.

5. The eNodeB performs transport differentiated flow control based on the adjusted

bandwidth of the transport resource group.

5.2 Transport Differentiated Flow Control

5.2.1 Overview

This section describes the feature LOFD-00301102 Transport Differentiated Flow Control.

When the bandwidth of the S1, X2, or eX2 interface is insufficient, the amount of data to be

transmitted may exceed the transmission capacity of the available bandwidth. Congestion

occurs in the following situations:

l On the S1 interface, transport overbooking is enabled. Non-real-time services are

admitted based on Min_GBR, but the actual traffic volume fluctuates and exceeds the

Min_GBR value. For details, see section 4.5 Transport Overbooking.

l On the X2 interface, the transient traffic volume of handover-related data is very high because of data bursts.

l On the eX2 interface, inter-eNodeB coordination data is transmitted and the traffic

volume is high.

Transport differentiated flow control provides users with DiffServ while ensuring fairness:

l DiffServ

When the transport bandwidth is limited, transport differentiated flow control uses the

following policies:

– It preferentially ensures the required bandwidth of non-flow-controllable services.

–

It then applies differentiation to non-real-time services. The bandwidth excludingthat reserved for Min_GBR is allocated among users based on their weight factors.

eRAN





51



l Fairness

Packet loss may occur on interface boards during congestion and affect fairness among

non-real-time services. For example, a service that establishes multiple Transmission

Control Protocol (TCP) connections preempts a service that has the same QCI but

establishes only a single TCP connection.Transport differentiated flow control ensures that each admitted user is allocated a

certain bandwidth based on the priority factor to prevent resource shortage. The priority

factor can be specified by STANDARDQCI.UlschPriorityFactor under the

STANDARDQCI MO (for standardized QCIs) or

STANDARDQCI.UlschPriorityFactor under the STANDARDQCI MO (for extended

QCIs).

In addition, transport differentiated flow control also ensures statistic accuracy of IP PM. For

details, see section 5.4 IP Performance Monitoring.

Transport differentiated flow control is applicable only to uplink data and involves the

following algorithms:

l Traffic shaping of transport resource groups

This algorithm ensures that the TX rate of a transport resource group does not exceed the

bottleneck bandwidth of the network and prevents network congestion.

l Queue scheduling of transport resource groups

Services are scheduled by PQ and WRR based on their weights. Each user has a weight

and therefore has a possibility to be scheduled.

l Back-pressure

This algorithm restricts the TX rates of non-real-time services to achieve differentiation.

Transport admission control and transport overload control restrict transport resourceoccupancy because the traffic of non-flow-controllable services is relatively stable.

5.2.2 Traffic Shaping

Traffic shaping limits traffic and decreases the packet loss rate when a network is congested.

Traffic shaping aims to limit the traffic and bursts from a connection. As a result, data packets

can be sent out at even rates.

Traffic shaping adopts the generic traffic shaping (GTS) technique and shapes irregular

streams or streams without predefined characteristics to match the upstream and downstream

bandwidths.

The token bucket (TB) principle applies to the GTS technique. Figure 5-2 shows the TB

principle.

eRAN





52



Figure 5-2 TB principle

The token bucket size determines the maximum number of tokens that can be buffered in the

bucket. Tokens are periodically generated by the token generator and injected into the token

bucket. When there is no token in the token bucket, packet transmission is not allowed. When

the token bucket is full, new tokens will be discarded.

Based on the TB principle, the eNodeB implements two levels of traffic shaping, which

consist of traffic shaping of transport resource groups and rate limiting on physical ports. With

these two types of traffic shaping, flow control is achieved.

Traffic Shaping of Transport Resource Groups

Traffic shaping of transport resource groups is a traffic rate limiting mechanism. It ensures

that the TX rate of a transport resource group does not exceed the admission bandwidth of the

transport resource group. To implement transport differentiated flow control, users can set the

RSCGRPALG.TXSSW parameter (TX traffic shaping switch for a transport resource group)

to ON(On) and then set the token injection rate and token bucket size.

The token injection rate and token bucket size in the following rate modes are represented as

follows:

l In single-rate mode, the token injection rate is specified by the RSCGRP.TXBW

parameter, and the token bucket size equals the sum of the values of the

RSCGRP.TXCBS and RSCGRP.TXEBS parameters.

l In dual-rate mode, the token injection rate and token bucket size are specified by the

RSCGRP.TXPIR and RSCGRP.TXPBS parameters, respectively.

eRAN





53



Rate Limiting on Physical Ports

Traffic shaping of transport resource groups is performed on the data link layer (MAC layer).

Rate limiting aims to limit the total rate of all the packets sent from a physical port regardless

of the type of data stream.

If an LR MO is configured for a physical port, the eNodeB uses the token bucket to process

all the packets sent from the physical port for flow control. If there are tokens in the token

bucket, the eNodeB allows burst transmission of packets. This simultaneously achieves flow

control and transmission of burst traffic.

The main parameters related to rate limiting on physical ports are LR .CIR, LR .CBS , and

LR . EBS . The token injection rate is specified by the LR .CIR parameter, and the token bucket

size is determined by the sum of the values of the LR .CBS and LR . EBS parameters. The

value of the LR .CBS parameter must be greater than or equal to that of the LR .CIR

parameter, and it is recommended that the LR . EBS parameter be set to 0.

If the buffer of the peer device can reach 1.5 or 2 times the value of the LR .CIR parameter, it

is recommended that the LR .CBS parameter be set to a value 1.5 to 2 times the value of the

LR .CIR parameter. If the buffer of the peer device is less than 1.5 times the value of the

LR .CIR parameter, it is recommended that the LR .CBS parameter be set to a value equaling

the buffer size of the peer device.

5.2.3 Queue Scheduling of Transport Resource Groups

Queue scheduling of transport resource groups ensures that non-flow-controllable services

(including real-time services, control plane services, OM MML services, and IP clock

services) are preferentially scheduled.

Each transport resource group can be configured with a maximum of seven queues, which are

classified into:

l PQ queues: queues numbered from 0 to RSCGRPALG. PQN minus 1, where

RSCGRPALG. PQN indicates the number of PQ queues.

l Non-PQ queues: queues numbered from RSCGRPALG. PQN to 7.

The queues in a transport resource group are scheduled as follows:

1. PQ queues are preferentially scheduled. A PQ queue with a smaller ID has a higher

scheduling priority. PQ queues with low priorities are scheduled only when those with

high priorities have no buffered data left.

2. If all PQ queues have been scheduled, the eNodeB performs WRR scheduling on non-

PQ queues. All non-PQ queues have the same scheduling weight.

Service packets enter queues based on their DSCPs. DSCPs and service types have a mapping

relationship, as described in section 3.6.2 Mapping Between Service Types and DSCPs.

Therefore, there is a mapping between service types and queues, as listed in Table 5-1. The

priority of queue x can be specified by the PRIx parameter, where x ranges from 0 to 6. Users

do not need to configure queue 7. For example, PRI2QUE. PRI3 indicates the lowest priority

of queue 3.

Table 5-1 lists the default mapping between service types and queues.

eRAN





54



Table 5-1 Default mapping between service types and queues

Service Type QCI Resource Type Queue ID

S1-U/X2-U 1 GBR 1

2 2

3 2

4 2

5 Non-GBR 1

6 4

7 4

8 4

9 6

eX2-U 4 - 2

8 - 4

9 - 6

S1-C/X2-C/eX2-C

(SCTP)

- - 0

OM (MML) - - 1

OM (FTP) - - 4

IP clock services - - 1

In addition to the default mapping, users can configure a mapping between service types and

DSCPs and between DSCPs and PQ queues to meet the requirements of differentiated flow

control. The mapping rules are as follows:

l Non-flow-controllable services enter PQ queues.

l Flow-controllable services enter non-PQ queues.

Otherwise, bandwidths cannot be guaranteed for non-flow-controllable services.

5.2.4 Back-Pressure Algorithm

The back-pressure algorithm limits the TX rates of uplink non-real-time services to prevent

congestion in a transport resource group. The eNodeB performs back-pressure on each

transport resource group. The RSCGRPALG.TCSW parameter decides whether to enable

back-pressure. Back-pressure is not applied to real-time services or passing-by data streams.

The back-pressure process is as follows:

l

The interface board detects that a transport resource group is congested and sends a back-pressure signal to the service board.

eRAN





55



l The service board buffers data of each non-real-time service separately and adjusts the

TX rate of each service.

NOTE

The initial TX rate is the result of multiplying UE-AMBR by 1.25. The UE-AMBR value is sent by the

MME to the eNodeB. The back-pressure algorithm will limit the TX rate of services. Therefore, whenthe back-pressure algorithm is enabled, the actual effect of the scheduling weight of transport resource

groups may be affected.

Figure 5-3 Back-pressure process for a non-real-time service

As shown in Figure 5-3, the back-pressure process is as follows:

1. The interface board periodically checks the buffer size of each queue in the transport

resource group.

2. When the duration for the data buffered in a queue exceeds the congestion threshold

(RSCGRPALG.CTTH ) at moment A, the queue and the corresponding transport

resource group enter the congestion state, which indicates that congestion has occurred.The interface board then sends congestion signals to the service board. The service board

stops transmitting the data for all non-real-time services in the transport resource group

and decreases the maximum data rates of all non-real-time services.

3. When the buffer size of a queue reaches the maximum value

(RSCGRPALG. DROPPKTNUM ), arriving data packets are discarded.

4. When the buffer size of a queue is less than the congestion clear threshold

(RSCGRPALG.CCTTH ) at moment B, the queue enters the congestion clear state. If all

the queues in a transport resource group enter the congestion clear state, the transport

resource group enters the congestion clear state. The interface board then sends

congestion clear signals to the service board. The service board retransmits the data for

non-real-time services in the transport resource group at a rate that is not greater than themaximum TX rate.

eRAN





56



5. In the congestion clear state, the back-pressure algorithm periodically increases the

maximum TX rate by the rate increase step, which is the difference between the TX rates

before and after the rate increase.

NOTE

The rate increase step of each service has a positive correlation with the weight factor

StandardQci.UlschPriorityFactor . For details about the weight factor, see Scheduling Feature

Parameter Description.

To avoid impacts of eX2 services on S1/X2 services, the eNodeB preferentially implements

back-pressure on eX2 services over S1/X2 services if transport resource groups become

congested.

When the back-pressure algorithm switch RSCGRPALG.TCSW is set to ENABLE(Enable)

in the case of insufficient transport resources, users can turn on the uplink Uu flow control

switch UlUuFlowCtrlSwitch under the ENodeBAlgoSwitch.TrmSwitch parameter to restrict

UE rates.

5.3 Dynamic Bandwidth Adjustment

Dynamic bandwidth adjustment is performed on each transport resource group. The dynamic

TX bandwidth adjustment switch is RSCGRPALG.TXBWASW .

NOTE

If the endpoint mode is not configured, all IP paths in a transport resource group must be referenced by

the eNodeBPath MO before dynamic bandwidth adjustment can be performed on this transport resource

group.

Table 5-2 lists the initial bandwidth available to each transport resource group. Users can

select a rate mode by setting the GTRANSPARA. RATECFGTYPE parameter.

Table 5-2 Initial bandwidths available to each transport resource group on different boards

Rate Mode Initial Available Bandwidth

Single-rate mode TX bandwidth (RSCGRP.TXBW )

Dual-rate mode PIR bandwidth (RSCGRP.TXPIR)

The dynamic bandwidth adjustment process is as follows:

1. The eNodeB periodically calculates the average packet loss rate of transport resource

groups.

– If the average exceeds the RSCGRPALG. PLRDTH value, the eNodeB decides

that the transport network is congested and reduces the available bandwidth of

transport resource groups, which cannot be lower than the

RSCGRPALG.TXBWAMIN value in single-rate mode or RSCGRP.TXCIR value

in dual-rate mode.

– If the average does not exceed the RSCGRPALG. PLRDTH value, the eNodeB

decides that the transport network is not congested and increases the available

bandwidth of transport resource groups, which cannot be higher thanRSCGRP.TXBW in single-rate mode or RSCGRP.TXPIR in dual-rate mode.

eRAN





57



Then, the eNodeB informs the transport differentiated flow control and transport

admission control algorithms.

2. The eNodeB periodically calculates the average delay variation of transport resource

groups.

If the available bandwidths adjusted based on the packet loss rate decrease average delay

variation in this period is greater than the RSCGRPALG. DDTH value, the eNodeB

decides that the transport network is congested, reduces the available bandwidths of the

transport resource groups, and then notifies the transport differentiated flow control and

transport admission control algorithms of the bandwidth adjustment. The adjusted

bandwidth cannot be lower than the RSCGRPALG.TXBWAMIN value in single-rate

mode or RSCGRP.TXCIR value in dual-rate mode.

Transport admission control ensures that the uplink admission bandwidths of transport

resource groups are not greater than the available bandwidths.

If the S-GW supports the downlink transport dynamic flow control, the dynamic RX

bandwidth adjustment switch (RSCGRPALG. RXBWASW ) can be turned on to ensure thatthe downlink admission bandwidths of transport resource groups are not greater than the

downlink available bandwidths. In single-rate mode, the minimum available bandwidth must

not be less than the RSCGRPALG. RXBWAMIN value. In dual-rate mode, the minimum

available bandwidth must not be less than the RSCGRP. RXCIR value.

NOTE

If the increase of delay variation or packet loss rate is caused by deteriorated transport network quality

rather than congestion of the transport network, enabling dynamic bandwidth adjustment will result in

mistaken data rate decreases. In this case, it is recommended that dynamic bandwidth adjustment be

disabled.

5.4 IP Performance Monitoring

For details about IP PM, see IP Performance Monitor Feature Parameter Description.

This section describes the feature LOFD-00301201 IP Performance Monitoring.

5.5 Mapping Between Algorithms and MOs

Table 5-3 shows the mapping between transport congestion control algorithms and MOs.

Table 5-3 Mapping between transport congestion control algorithms and MOs

Level 1 Algorithm Level 2 Algorithm MO

Transport differentiated flow

control

Traffic shaping RSCGRPALG, RSCGRP,

and LR

Queue scheduling PRI2QUE and

RSCGRPALG

Back-pressure RSCGRPALG

Transport dynamic flow

control

Dynamic bandwidth

adjustment

RSCGRPALG and

IPPMSESSION

eRAN





58



Level 1 Algorithm Level 2 Algorithm MO

IP PM IPPMSESSION

eRAN





59



6 Application Scenarios

This chapter describes the use of the TRM algorithms in different scenarios.

eRAN


Description 6 Application Scenarios



60



6.1 Different Transport Paths Based on QoS Grade

6.1.1 Overview

This section describes the feature LOFD-003016 Different Transport Paths based on QoS

Grade.

Flow-controllable services are admitted based on Min_GBR. The actual bit rates of these

services, however, may be far greater than the Min_GBR value. Assume that most services

are flow-controllable and they are preferentially admitted to transport resource groups on the

primary path. In this situation, transport resource groups on the secondary path are used only

if there are excessively high loads on the primary path. As a result, traffic volumes on the two

paths are not balanced. To solve this problem, the Different Transport Paths Based on QoS

Grade feature is introduced.

Services can be allocated different transport paths based on their QoS grade in a hybrid

transmission scenario shown in Figure 6-1. In this scenario, two transport paths with different

QoS grades are configured between the eNodeB and the S-GW. Services with different QCIs

are allocated different transport paths for load balancing.

Figure 6-1 Hybrid transmission

As shown in Figure 6-1, IPPATHRT.TRANRSCTYPE is set to HQ(High Quality) and

LQ(Low Quality) for the two paths, indicating high and low QoS grades, respectively. The path with a higher QoS grade provides lower bandwidth for a few services with high QoS

requirements, and the path with a lower QoS grade provides higher bandwidth for a large

number of services with low QoS requirements. This helps operators reduce operating

expense (OPEX).

In a hybrid transmission scenario, transport resources cannot be configured in endpoint mode.

6.1.2 Process of Implementing Different Transport Paths Based onQoS Grade

When the Different Transport Paths Based on QoS Grade feature is implemented, servicerequests are not always admitted on the primary path. Instead, the eNodeB decides whether to

eRAN





61



admit a service on the primary or secondary path based on the admission control algorithm for

hybrid transmission. This improves transport resource efficiency and user experience.

The Different Transport Paths Based on QoS Grade feature is implemented on transport

resource groups. The process for admitting a service request is as follows:

1. The eNodeB determines all the transport resource groups on the primary and secondary

paths.

2. The eNodeB calculates the primary path load ratio and the secondary path load ratio

using the following formulas:

– Primary path load ratio = Total downlink transport load of all primary groups / Total

downlink available bandwidth of all primary groups

– Secondary path load ratio = Total downlink transport load of all secondary groups /

Total downlink available bandwidth of all secondary groups

3. The service is preferentially admitted on the secondary path if the following conditions

are met:

– Primary path load ratio > UDTPARAGRP. PRIMPTLOADTH

– Primary path load ratio x UDTPARAGRP. PRIM2SECPTLOADRATH >

Secondary path load ratio

If the service is not admitted, it attempts the primary path.

4. The service is preferentially admitted on the primary path if the following conditions are

met:

– Primary path load ratio ≤ UDTPARAGRP. PRIMPTLOADTH

– Primary path load ratio x UDTPARAGRP. PRIM2SECPTLOADRATH ≤

Secondary path load ratio

If the service is not admitted, it attempts the secondary path.


The parameters related to Different Transport Paths Based on QoS Grade are as follows:

l UDTPARAGRP. PRIMPTLOADTH : primary path load threshold for services of a user

data type.

l UDTPARAGRP. PRIM2SECPTLOADRATH : threshold of the primary-to-secondary

port load ratio for services of a user data type.

l The transport resource type IPPATHRT.TRANRSCTYPE carried by different transport

paths indicates the type of transport resources carried by routes in hybrid transmissionscenarios.

6.2 User Data Type

For an extended user data type, the UDT and UDTPARAGRP MOs must be configured with

the UDT.UDTPARAGRPID and UDTPARAGRP.UDTPARAGRPID parameters set to the

same value. The parameters for configuring the transport parameter group of an extended user

data type are the same as those for configuring the transport parameter group of a standard

user data type, as listed in Table 3-8.

Algorithms and principles for extended QCIs are the same as those for standardized QCIs.Table 6-1 describes the main configuration items of extended QCIs.

eRAN





62



Table 6-1 Main configuration items of extended QCIs

Function Configuration Item ConfigurationDescription

DiffServ Priority rule DIFPRI. PRIRULE is set toDSCP.

Transport admission control l Flow control type

l Activity factor

l Primary transport

resource type

l Primary port load

threshold

l Threshold ratio of

primary to secondary

port loads

l Min_GBR

Min_GBR indicates the

minimum GBR configured

for each QCI in the uplink

or downlink on the Uu

interface. The involved

parameters are

StandardQci.UlMinGbr ,

ExtendedQci.UlMinGbr ,

StandardQci. DlMinGbr

andExtendedQci. DlMinGbr .

Differentiated flow control Weight factor for uplink

scheduling

(ExtendedQci.UlschPriorit

yFactor ) in the

ExtendedQci MO.

None

6.3 RAN Sharing In the RAN sharing scenario, it is recommended that each operator be configured with a

transport resource group. Common algorithms are used in this scenario.

6.4 Base Station Cascading

In base station cascading scenarios, a separate transport resource group is recommended for

lower-level base stations. Common algorithms are used in this scenario.

eRAN





63



7 Related Features

7.1 Features Related to LBFD-00300201 DiffServ QoSSupport

Prerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

None

7.2 Features Related to LOFD-00301101 TransportOverbooking


None


None

Impacted Features

None

eRAN


Description 7 Related Features



64



7.3 Features Related to LOFD-00301102 TransportDifferentiated Flow Control


None


None

Impacted Features

None

7.4 Features Related to LOFD-00301103 TransportResource Overload Control


None


None

Impacted Features

None

7.5 Features Related to LOFD-00301201 IP PerformanceMonitoring


None


None

Impacted Features

None

eRAN





65



7.6 Features Related to LOFD-00301202 TransportDynamic Flow Control


l Transport Dynamic Flow Control requires LOFD-00301102 Transport Differentiated

Flow Control. When Transport Dynamic Flow Control is enabled, transmission boards in

the eNodeB may be congested, and therefore Transport Differentiated Flow Control must

also be enabled.

l Transport Dynamic Flow Control requires LOFD-00301201 IP Performance Monitoring.


None

Impacted Features

None

7.7 Features Related to LOFD-003016 Different TransportPaths based on QoS Grade


None


None

Impacted Features

None

eRAN





66



8 Network Impact

8.1 LBFD-00300201 DiffServ QoS Support

System Capacity

No impact.

Network Performance

DiffServ QoS Support meets different QoS requirements of different services, prioritizing the

QoS requirements of high-priority services.

8.2 LOFD-00301101 Transport Overbooking

System Capacity

Transport Overbooking enables the network to admit services that would otherwise be refused

due to resource limits. Under Transport Overbooking, the sum of the maximum rates of all

admitted services can exceed the transport bandwidth.

Network Performance

No impact.

8.3 LOFD-00301102 Transport Differentiated Flow Control

System Capacity

No impact.

Network Performance

Transport Differentiated Flow Control enables eNodeBs to provide differentiated services andhelps ensure fairness among users.

eRAN


Description 8 Network Impact



67



8.4 LOFD-00301103 Transport Resource Overload Control

System Capacity

When unexpected overloads occur, Transport Resource Overload Control can be used to

enhance transmission stability.

Network Performance

No impact.

8.5 LOFD-00301201 IP Performance Monitoring

System Capacity

No impact.

Network Performance

No impact.

8.6 LOFD-00301202 Transport Dynamic Flow Control

System Capacity

No impact.

Network Performance

In scenarios where transport bandwidths dynamically change, Transport Dynamic Flow

Control can be used to prevent network congestion and ensure transmission QoS.

8.7 LOFD-003016 Different Transport Paths based on QoSGrade

System Capacity

No impact.

Network Performance

No impact.

eRAN


Description 8 Network Impact



68



9 Engineering Guidelines

This chapter provides engineering guidelines for transport resource management.

eRAN


Description 9 Engineering Guidelines



69



9.1 When to Use Transport Resource Management

9.1.1 Transport Resource Configurations and Mapping

Physical Ports

For details about how to configure physical ports, see S1/X2 Self-Management Feature

Parameter Description and eX2 Self-Management Feature Parameter Description.

Transport Resource Groups

Each physical port has a default transport resource group. Before users modify the default

transport resource group or check the performance counters in the default transport resourcegroup, users must add the default transport resource group manually. In link mode, an IP path

that is not assigned to a dedicated transport resource group is by default managed by a default

transport resource group. In endpoint mode, an endpoint for user plane peer or end point

group that is not assigned to a dedicated transport resource group is by default managed by a

default transport resource group.

In RAN sharing scenarios, it is recommended that transport resource groups be specified for

each operator.

In cascading scenarios, a separate transport resource group must be configured for lower-level

eNodeBs. The lower-level eNodeBs do not share a group with the local eNodeB.

IP Paths

If the Different Transport Paths Based on QoS Grade feature is planned for a network, two

transport paths must be configured. Otherwise, only one transport path is required.

The Different Transport Paths Based on QoS Grade feature requires that a primary IP path and

a secondary IP path with different transport resource groups be configured between an

eNodeB and an S-GW. Traffic is divided between the two paths to ensure a fair usage of

primary and secondary resources. This feature also requires an extra IP address, which is used

as the local IP address of the secondary IP path. This feature is optional.

Endpoints

For details about how to configure endpoints, see S1/X2 Self-Management Feature Parameter

Description and eX2 Self-Management Feature Parameter Description.

DiffServ QoS

The mapping between services and transport resources is implemented based on the overall

DSCP plan to ensure DiffServ QoS. eNodeBs support the mapping function by default. The

mapping must be activated.

eRAN





70




Transport Admission Control

If transport resources are insufficient, an eNodeB controls access requests. By controllingaccess requests, the transport admission control feature ensures the transmission quality of

ongoing services.

This feature is enabled by default. It is recommended that this feature be kept enabled.

Transport Overbooking

As a benefit of transport admission control, transport overbooking can also be enabled. If the

activity factor for a type of service is less than 100%, overbooking works. If the activity factor

is 100%, however, overbooking does not work.

For transport resource groups, a smaller activity factor indicates a lower bandwidth reservedfor services and higher overbooking gains. A smaller activity factor also indicates a higher

probability that too many services are admitted and a lower probability that the quality of

services (such as GBR services) is ensured. Transport resource group overbooking is optional.

If physical port overbooking is used, the sum of the admission bandwidths of all the transport

resource groups on a physical port can be greater than the bandwidth of the physical port to

increase the system capacity. However, excessive services may be admitted. To control

service admission, you are advised to enable admission control on physical ports. To ensure

that non-GBR services can be admitted successfully and will not be preempted or released

when overload occurs, set the corresponding activity factor to 0.

Physical port overbooking is optional.

Transport Resource Preemption

To reduce service admission failures caused by insufficient transport resources, the eNodeB

can trigger transport resource preemption. This feature enables high-priority services to

preempt resources of low-priority services. This increases the access success rate for high-

priority services but increases the service drop rate for low-priority services.

This feature is optional and disabled by default.

Transport Load Reporting

The transport load reporting algorithm monitors system transport loads. If transport loads are

too high, this algorithm reports the load status to the transport overload control algorithm and

the radio interface load balancing algorithm. For details about the radio interface load

balancing algorithm, see Mobility Load Balancing Feature Parameter Description.

Transport load reporting is available only if the radio interface load balancing algorithm is

enabled.

Transport Overload Control

In a transport resource overload situation, the bandwidth reserved for ongoing services cannot

be ensured because of excessive transport loads. The transport overload control feature periodically checks whether transport resources are insufficient. If transport resources are

eRAN





71



insufficient, the eNodeB releases preemptable services that have lower ARPs and request

higher bandwidth.

This feature is enabled by default. It is recommended that this feature be kept enabled.


Transport Differentiated Flow Control

The transport differentiated flow control feature ensures that the actual traffic volume does

not exceed the transport resource group bandwidth and physical port bandwidth. This prevents

network congestion and reduces packet loss. If this feature is used, bandwidths are

preferentially allocated to non-flow-controllable services. Then, provided that the Min_GBR

is ensured, the remaining bandwidths are allocated to flow-controllable services based on the

weight factors specified by the StandardQci.UlschPriorityFactor ,

ExtendedQci.UlschPriorityFactor , StandardQci. DlschPriorityFactor and

ExtendedQci. DlschPriorityFactor parameters. Transport differentiated flow control caninclude traffic shaping, queue scheduling and back-pressure. It is recommended that transport

differentiated flow control be enabled.

Transport Dynamic Flow Control

In scenarios where transport bandwidths dynamically change, the bandwidths available to

bottleneck transmission nodes on the transport network may be less than the TX bandwidths

configured for transport resource groups or LR bandwidths configured for physical ports on

the eNodeB. In this situation, if both admission control and flow control are performed on

transport resource groups based on the configured TX bandwidths, the transport network may

be congested. The transport dynamic flow control feature estimates the bottleneck bandwidth

of the transport network based on transmission quality monitored using IP PM. The TX ratesof the transport resource groups on interface boards in the eNodeB are adjusted dynamically

to limit the TX rates within the capacity of the bottleneck bandwidth.

Transport dynamic flow control prevents transport network congestion to ensure transmission

QoS in scenarios where transport bandwidths dynamically change. This feature increases

system overhead and requires that the EPC support IP PM. This feature is optional and

disabled by default.

9.2 Required Information

9.2.1 Transport Bandwidth Planned by Operators

The transport bandwidth between the eNodeB and the EPC affects the TX/RX bandwidth and

the transmission QoS policies of the eNodeB.

To prevent packet loss on transport links due to congestion where the transport bandwidth

planned by operators is insufficient, users can limit the rate on the eNodeB or limit the TX

bandwidth of transport resource groups.

9.2.2 Transport Resource Mapping

Transmission QoS planning of an operator must be obtained for transport resource mapping.The planning involves QCIs, DSCPs of signaling and service packets, and VLAN priorities.

eRAN





72



Transport resource mapping on the eNodeB side consists of the following:

l Mapping of control-plane packets, user-plane packets, OM packets, and IP clock packets

to DSCPs

l

Mapping of user data types to QCIs (including standardized and extended QCIs)l (Optional) Mapping of QCIs of user data types to IP paths

l Mapping of DSCPs to VLAN priorities

For more information, see section 3.6.2 Mapping Between Service Types and DSCPs.

9.3 Planning

To implement different transport paths, at least two local IP addresses must be planned for the

user plane. If two physical ports are involved in different transport paths, the two ports

provide outgoing traffic simultaneously. If only one physical port is involved in different

transport paths, this port provides outgoing traffic and two transport resource groups must be

configured on this port.

If different transport paths do not need to be implemented, no special network planning is

required.

9.4 Overall Deployment Procedure

None

9.5 Deployment of Transport Resource Configurations andMapping

9.5.1 Process

None

9.5.2 Requirements

Operating Environment

None

Transmission Networking

None

License

The operator has purchased and activated the license for the feature listed in following table.

eRAN





73



Feature ID Feature Name Model LicenseControl Item

NE Sales Unit

LOFD-0030

16

Different

Transport Paths

based on QoS

Grade

LTIS0D

TPQG0

0

Different

Transport Paths

based on QoS

Grade(FDD)

eNod

eB

per eNodeB

LOFD-0030

11

Enhanced

Transmission

QoS

Management(FD

D)

LT1SET

QOSM0

0

Enhanced

Transmission

QoS

Management(F

DD)

eNod

eB

per eNodeB

LOFD-0030

12

IP Performance

Monitoring

LT1S0I

PAPM0

0

IP Performance

Monitoring(FD

D)

eNod

eB

per eNodeB

9.5.3 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is

data that you must collect for all scenarios. Collect scenario-specific data when necessary for

a specific feature deployment scenario.

There are three types of data sources:

l Network plan (negotiation required): parameter values planned by the operator and

negotiated with the EPC or peer transmission equipment

l Network plan (negotiation not required): parameter values planned and set by the

operator

l User-defined: parameter values set by users

Required Data

Standardized QCIs and Extended QCIs

For details about data preparation for standardized QCIs and extended QCIs, see QoS

Management Feature Parameter Description.

Transport Resources

Parameters related to transport resource configuration are in the following managed objects

(MOs):

l IPPATH and RSCGRP

These two MOs are basic for user plane data transmission and transport resource

management.

l GTRANSPARA

In this MO, the rate mode can be set to single-rate mode or dual-rate mode. Different

modes require different transport load control and transport congestion controlalgorithms.

eRAN





74



l UDT, UDTPARAGRP, and DIFPRI

Parameters in these MOs determine how various types of services are mapped to

transport resources. Different QoS priorities are provided for different types of services.

l IPPATHRT

Parameters in this MO specify an IP path route for transport load balancing. This MO

along with the MOs DIFPRI, IPPATH, RSCGRP, UDT, and UDTPARAGRP

implement the Different Transport Paths Based on QoS Grade feature.

l EP2RSCGRP

Parameters in this MO can be configured to add the endpoint group containing the local

and peer user plane IP addresses to a user-defined transport resource group,

implementing the mapping between user plane data and a transport resource group.

Of the preceding parameters, only the parameters in the IPPATHRT MO are scenario-

specific. Other parameters are necessary for all scenarios. The following describes how to

collect data related to these MOs.

l Global Transport Parameters

The following table describes the parameters that must be set in the GTRANSPARA

MO to configure the global transport parameters within an eNodeB.

eRAN





75



ParameterName

ParameterID

Data Source Setting Notes

Resource

Group

Scheduling

Weight Switch

GTRANSPA

RA. LPSCHS

W

Network plan

(negotiation not

required)

For single-rate mode:

lIf you set this parameter toDISABLE(Disable), the

physical port overbooking

switches are turned off, the


switches are turned off, and

the total TX bandwidth of

the transport resource

groups is greater than that of

the physical port, then the

TX bandwidth allocated to a

group is directly

proportional to thatconfigured for this group.

l If you set this parameter to

ENABLE(Enable), the


switches are turned off, and

the total TX bandwidth of

the transport resource



TX bandwidth allocated to a

group is directly

proportional to the

scheduling weight

configured for this group.

For dual-rate mode:

l If the total CIR bandwidth

of the transport resource



CIR bandwidth allocated to

a group is directly

proportional to that

configured for this group.

l If the total CIR bandwidth

of the transport resource

groups is less than that of

the physical port and the


switches are turned off, the

non-CIR bandwidth

allocated to a group is

directly proportional to the

scheduling weight

configured for this group. In

eRAN





76



ParameterName

ParameterID


this case, the PIR bandwidth

is equal to the sum of the

CIR and allocated non-CIR

bandwidths.

Rate Config

Type

GTRANSPA

RA. RATECF

GTYPE

Network plan

(negotiation not

required)

Set this parameter based on the

network plan.

The default value is

SINGLE_RATE(Single Rate).

Set this parameter to

DUAL_RATE(Dual Rate) in

multi-operator scenarios where

more precise TRM is required.

l Transport Resource Groups for User Plane Data

The following table describes the parameters that must be set in RSCGRP MOs to

configure transport resource groups on the S1, X2, or eX2 user plane belong.

ParameterName

ParameterID


Transport

Resource

Group ID

RSCGRP. R

SCGRPID

User-defined Set this parameter based on the

network plan.

It is recommended that

transport resource groups beconfigured separately for

different operators. If there is

no special requirement for a

default transport resource

group, this default group does

not need to be added. If

counters related to a default

transport resource group are

required, this default group

must be added.

eRAN





77



ParameterName

ParameterID


Tx Bandwidth RSCGRP.T

XBW

Network plan

(negotiation not

required)


actual user-configured transport

bandwidth.

This parameter specifies the

maximum TX bandwidth of the

transport resource group. This

parameter is used for admission

control and traffic shaping.

This parameter is valid when

the

GTRANSPARA. RATECFGT

YPE parameter in the

GTRANSPARA MO is set to

SINGLE_RATE(SingleRate).

Rx Bandwidth RSCGRP. R

XBW

Network plan

(negotiation not

required)


actual user-configured transport

bandwidth.


maximum RX bandwidth of the


parameter is used for admission

control. This parameter is valid

when the

GTRANSPARA. RATECFGT YPE parameter in the


SINGLE_RATE(Single

Rate).

TX Committed

Burst Size

RSCGRP.T

XCBS

Network plan

(negotiation not

required)

None

TX Excessive

Burst Size

RSCGRP.T

XEBS

Network plan

(negotiation not

required)

None

Operator ID RSCGRP.OI

D

Network plan

(negotiation not

required)


network plan.


operator to which the transport

resource group belongs.

eRAN





78



ParameterName

ParameterID


Scheduling

Weight

RSCGRP.W

EIGHT

Network plan

(negotiation not

required)


network plan.


scheduling weight for the


weight is used if the total

bandwidth of the resource

groups on a physical port

exceeds the bandwidth of this

port. The default value is

recommended.

TX Committed

InformationRate

RSCGRP.T

XCIR

Network plan

(negotiation notrequired)


network plan.This parameter specifies the

TX CIR bandwidth of the

transport resource group. The

value indicates a TX rate

committed to the operator. This

parameter is used for uplink

admission control and

scheduling of non-flow-

controllable services. This

parameter is valid when the


YPE parameter in theGTRANSPARA MO is set to

DUAL_RATE(Dual Rate).

RX Committed

Information

Rate

RSCGRP. R

XCIR

Network plan

(negotiation not

required)


network plan.


RX CIR bandwidth of the

transport resource group. The

value indicates an RX rate

committed to the operator. This

parameter is used for downlink

admission control of non-flow-

controllable services. This

parameter is valid when the





eRAN





79



ParameterName

ParameterID


TX Peak

Information

Rate

RSCGRP.T

XPIR

Network plan

(negotiation not

required)


network plan.

This parameter is used for

uplink admission control,

scheduling, and traffic shaping

of all services. This parameter

is valid when the





RX Peak

InformationRate

RSCGRP. R

XPIR

Network plan



network plan.This parameter is used for

downlink admission control of

all services. This parameter is

valid when the





TX Peak Burst

Size

RSCGRP.T

XPBS

Network plan

(negotiation not

required)

None

NOTE

l For LTE, configure the CIR- and PIR-related parameters of the transport resource groups on the

physical ports of the backplane, and use the dual-rate mode. With these settings, LTE implements

admission control based on TX CIR, TX PIR, RX CIR, and RX PIR.

l If the GSM side manages a GSM/LTE dual-mode base station, set

BTSGTRANSPARA.RATECFGTYPE to DUAL_RATE(Dual Rate) and set the dual-rate-related

parameters using BTSIPLGCPORT.TXCIR , BTSIPLGCPORT.TXPIR ,

BTSIPLGCPORT.TXCBS , BTSIPLGCPORT.TXPBS, and BTSIPLGCPORT.WEIGHT for the

UTRPc. The parameter settings for the UTRPc enable the scheduling and rate limiting based on

RSCGRP.TXCIR, RSCGRP.TXPIR, RSCGRP.TXCBS , RSCGRP.TXPBS , andRSCGRP.WEIGHT for LTE. For details about the preceding GSM parameters, see BSC6900 GSM

Parameter Reference.

l IP Paths for User Plane Data

The following table describes the parameters that must be set in IPPATH MOs to

configure IP paths on the user plane between eNodeBs and S-GWs or between eNodeBs.

Parameter Name Parameter ID Data Source Setting Notes

IP Path ID IPPATH. PATHID User-defined Set this parameter

based on the

network plan.

eRAN





80




Join Transport

Resource Group

IPPATH. JNRSCG

RP

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

If this parameter is

set to

ENABLE(Enable)

, the IP path is

assigned to and

managed by a

dedicated transport

resource group. If

this parameter is

set to

DISABLE(Disable

), the IP path isassigned to and

managed by a

default transport

resource group. It

is recommended

that this parameter

be set to

ENABLE(Enable)

to facilitate

transport resource

management.

Transport Resource

Group ID

IPPATH. RSCGRP

ID

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

must be already set

in the associated

RSCGRP MO.

Local IP IPPATH. LOCALI

P

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the local

IP address of the IP

path. This

parameter must be

already set in the

associated DEVIP

MO.

eRAN





81




Peer IP IPPATH. PEERIP Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the IP

address of the peer

network element

(NE) (such as an S-

GW) of the IP path.

Path Type IPPATH. PATHTY

PE

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the DSCPtype of the IP path.

It is recommended

that this parameter

be set to

ANY(ANY QOS).

DSCP IPPATH. DSCP Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

If the

IPPATH. PATHTY

PE parameter is setto FIXED(FIXED

QOS), the

IPPATH. DSCP

parameter must be

set.

IPMUXSWITCH IPPATH. IPMUXS

WITCH

Network plan

(negotiation not

required)

Use the default

value.

l QoS Priorities for Different Services

The QoS priority must be configured for different services.

The priorities of the signaling, OM data, and IP clock packets are configured in the

DIFPRI MO. Default values are available for the parameters in this MO, and users can

modify the values but cannot add or remove such an MO.

The QoS priorities for services with QCIs 1 to 9 are configured in the UDT and

UDTPARAGRP MOs.

The following table describes the parameters that must be set in the DIFPRI MO.

eRAN





82




Priority Rule DIFPRI. PRIRUL

E

Network plan

(negotiation not

required)

This parameter

specifies the rule

for prioritizing

traffic to meet

service

requirements. If

this parameter is

set to

IPPRECEDENC

E(IP Precedence),

the eNodeB

converts type of

service (ToS)

values to DSCPs

and then prioritizestraffic.

Signaling Priority DIFPRI. SIGPRI Network plan

(negotiation

required)

Set this parameter

based on the

network plan.

This parameter

specifies the QoS

priority of

signaling. The

default value is

recommended.

OM High Priority DIFPRI.OMHIG

HPRI

Network plan

(negotiation

required)

Set this parameter

based on the

network plan.

This parameter

specifies the QoS

priority of high-

level OM data. The

default value is

recommended.

OM Low Priority DIFPRI.OMLOW

PRI

Network plan

(negotiationrequired)

Set this parameter

based on thenetwork plan.

This parameter

specifies the QoS

priority of low-

level OM data, that

is, FTP services.


recommended.

eRAN





83




IP Clock Priority DIFPRI. IPCLKPR

I

Network plan

(negotiation

required)

Set this parameter

based on the

network plan.

This parameter

specifies the QoS

priority of IP clock

data. The default

value is

recommended.

The following table describes the parameters that must be set in the UDT MO.


User Data Type

Number

UDT.UDTNO Network plan

(negotiation not

required)

This parameter

specifies the number

of a user data type,

which can be set to a

value indicating a

standardized or

extended QCI. The

default value is

recommended.

User Data Type

Transfer Parameter Group ID

UDT.UDTPARAGR

PID

Network plan


This parameter

specifies the ID of the transport

parameter group

corresponding to a

user data type. Set

this parameter based

on the network plan.


recommended.

The following table describes the parameters that must be set in the UDTPARAGRP MO.

eRAN





84




User Data Type

Transfer Parameter

Group ID

UDTPARAGRP.U

DTPARAGRPID

Network plan

(negotiation not

required)

This parameter

specifies the ID of

the transport

parameter group

corresponding to a

user data type,

which has a one-to-

one mapping with

the

UDT.UDTPARAGR

PID parameter. The

default value is

recommended.

Priority UDTPARAGRP. P

RI

Network plan

(negotiation not

required)

This parameter

specifies the QoS

priority of the

transport parameter

group corresponding

to a user data type.

Set this parameter

based on the

network plan. The

default value is

recommended.

Primary Transport

Resource Type

UDTPARAGRP. P

RIMTRANRSCTYP

E

Network plan


This parameter

specifies the type of primary transport

resource in the

transport parameter

group corresponding

to a user data type in

a hybrid

transmission

scenario. Set this

parameter based on

the network plan.


recommended.

eRAN





85




Primary Port Load

Threshold(%)

UDTPARAGRP. P

RIMPTLOADTH

Network plan

(negotiation not

required)

This parameter

specifies the primary

port load threshold

for the transport

parameter group

corresponding to a

user data type in a

hybrid transmission

scenario. Set this

parameter based on

the network plan.


recommended.

Primary To

Secondary Port

Load Ratio

Threshold(%)

UDTPARAGRP. P

RIM2SECPTLOAD

RATH

Network plan

(negotiation not

required)

This parameter

specifies the

primary-to-

secondary port load

ratio threshold for

the transport

parameter group

corresponding to a

user data type in a

hybrid transmission

scenario. Set this

parameter based on

the network plan.The default value is

recommended.

l Mapping Between Endpoints and Transport Resource Groups

The mapping between endpoints and transport resource groups can be configured in an

EP2RSCGRP MO. If the mapping is not configured, the default transport resource group is

used. If the mapping is configured, the specified transport resource group is used. The

following table describes the parameters that must be set in the EP2RSCGRP MO.


Node Identifier EP2RSCGRP. END

POINTID

Network plan

(negotiation not

required)

Use the default

value.

Transport Resource

Group ID

EP2RSCGRP. RSC

GRPID

Network plan

(negotiation not

required)

Use the default

value.

eRAN





86



Scenario-specific Data

To configure the Different Transport Paths Based on QoS Grade feature, the

UDTPARAGRP, DIFPRI, RSCGRP, IPPATH, and IPPATHRT MOs must be configured.

The configurations of the UDTPARAGRP, DIFPRI, RSCGRP, and IPPATH MOs are

already described in Required Data. The following table describes the parameters that must

be set in an IPPATHRT MO.

Different Transport Paths Based on QoS Grade


Source IP IPPATHRT. SRCIP Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the local IP

address of the IP path route. This

parameter must be

already set in the

associated DEVIP

MO.

Destination IP IPPATHRT. DSTIP Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the

destination IP

address of the IP

path route.

Transport Resource

Type

IPPATHRT.TRAN

RSCTYPE

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

Next Hop IP IPPATHRT. NEXT

HOPIP

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies the next-hop IP address of

the IP path route.

9.5.4 Precautions

Before changing the TX or RX bandwidth of a default transport resource group, you must add

another default transport resource group. Otherwise, the change will fail.

eRAN





87



9.5.5 Hardware Adjustment

N/A

9.5.6 Initial ConfigurationUsing the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 9-1 in a summary data file, which also

contains other data for the new eNodeBs to be deployed. Then, import the summary data file

into the Configuration Management Express (CME) for batch configuration. For detailed

instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for

the eNodeB.

The summary data file may be a scenario-specific file provided by the CME or a customized

file, depending on the following conditions:

l The managed objects (MOs) in Table 9-1 are contained in a scenario-specific summary

data file. In this situation, set the parameters in the MOs, and then verify and save the

file.

l Some MOs in Table 9-1 are not contained in a scenario-specific summary data file. In

this situation, customize a summary data file to include the MOs before you can set the

parameters.

eRAN





88



Table 9-1 Parameters related to transport resource configurations and mapping

MO Sheet in theSummary DataFile

Parameter Group Remarks

RSCGRP Base Station

Transport Data or

user-defined sheet

Cabinet No.,

Subrack No., Slot

No., Transport

Resource Group

Bear Type,

Subboard Type,

Bearing Port Type,

Bearing Port No.,

Transport Resource

Group ID, Rate

Unit, Tx

Bandwidth, RxBandwidth, TX

Committed Burst

Size(Kbit), TX

Excessive Burst

Size(Kbit),

Operator ID,

Scheduling Weight,

TX Committed

Information Rate,

RX Committed

Information Rate,

TX Peak Information Rate,

RX Peak

Information Rate,

TX Peak Burst

Size(Kbit)

The summary data

file needs to be

customized based

on the template

named

En_Basic_eRAN_

Sharing_Link.

eRAN





89





IPPATH IP Path Cabinet No.,

Subrack No., Slot

No., Subboard

Type, Port No., IP

Path ID, Join

Transport Resource

Group, Transport

Resource Group

ID, Path Type,

DSCP, Local IP,

Peer IP, Transport

Resource Type,

Path check,IPMUX Switch

Flag, Max

Subframe length,

Max frame length,

Max Timer,

Description Info

-

GTRANSPARA Base Station

Transport Data or

user-defined sheet

Resource Group

Scheduling Weight

Switch, Rate

Config Type

The summary data

file needs to be

customized based

on the template

namedEn_Basic_eRAN_

Sharing_Link.

DIFPRI Base Station

Transport Data

Priority Rule,

Signaling Priority,

OM High Priority,

OM Low Priority,

IP Clock Priority

The summary data

file needs to be

customized based

on the template

named

En_Basic_eRAN_

Sharing_Link.

IPPATHRT Base Station

Transport Data or user-defined sheet

Source IP,

Destination IP,Transport Resource

Type, Next Hop IP

The summary data

file needs to becustomized based

on the template

named

En_Basic_eRAN_

Sharing_Link.

eRAN





90





UDT Base Station

Transport Data or

user-defined sheet

User Data Type

number, User Data

Type Transfer

Parameter Group

ID.

The summary data

file needs to be

customized based

on the template

named

En_Basic_eRAN_

Sharing_Link.

UDTPARAGRP Base Station

Transport Data or

user-defined sheet

User Data Type

Transfer Parameter

Group ID., Priority

Rule, Priority, Act

Factor, Primary

Transport Resource

Type, Primary Port

Load Threshold,

Primary To

Secondary Port

Load Ratio

Threshold, Flow

Control Type

The summary data

file needs to be

customized based

on the template

named

En_Basic_eRAN_

Sharing_Link.

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on

existing eNodeBs. This method reconfigures all data, except neighbor relationships, for

multiple eNodeBs in a single procedure. The procedure is as follows:

Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the

CME to Perform Batch Configuration for Newly Deployed eNodeBs". For online help, press

F1 when a CME window is active, and select Managing the CME > CME Guidelines >

LTE Application Management > eNodeB Related Operations > Customizing a Summary

Data File for Batch eNodeB Configuration.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk

Configuration Data (U2000 client mode), or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB

data stored on the CME into the customized summary data file.

Step 3 In the summary data file, set the parameters in the MOs according to the setting notes

provided in section "Data Preparation" and close the file.

Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk

Configuration Data (U2000 client mode), or choose LTE Application > Import Data >

Import Base Station Bulk Configuration Data (CME client mode), to import the summary

data file into the CME, and then start the data verification.

Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental

Scripts (U2000 client mode), or choose Area Management > Planned Area > ExportIncremental Scripts (CME client mode), to export and activate the incremental scripts. For

eRAN





91



detailed operations, see Managing the CME > CME Guidelines > Script File Management

> Exporting Incremental Scripts from a Planned Data Area in the CME online help.

----End

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.

The procedure is as follows:

Step 1 In the planned data area, click Base Station in the upper left corner of the configuration

window.

Step 2 In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong.

Figure 9-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.

Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are

displayed in area 4.

Step 5 Set the parameters in area 4 or 5.

Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose

Area Management > Planned Area > Export Incremental Scripts (CME client mode), to

export and activate the incremental scripts.

----End

Using MML Commands

In endpoint mode, run the ADD EPGROUP, ADD USERPLANEHOST, ADDUSERPLANEPEER , ADD UPHOST2EPGRP, ADD UPPEER2EPGRP, and ADD S1

eRAN





92



commands to configure transport links for user plane data. For details, see S1/X2 Self-

Management Feature Parameter Description.

In link mode, the configuration procedure is as follows:

Step 1 Run the SET GTRANSPARA command to set the rate mode for the eNodeB and thescheduling weight switch for transport resource groups.

Step 2 Run the ADD RSCGRP command to add a transport resource group for user plane resource

management.

Step 3 Run the ADD IPPATH command to add an IP path.

Step 4 Run the SET DIFPRI command to set the priorities of the signaling, OM, and IP clock

services. Run the MOD UDT and MOD UDTPARAGRP commands to set the priorities of

differentiated user data.

Unless there are special requirements, retain the default values.

Step 5 Run the ADD IPPATHRT command to add an IP path route.

Assume that the RSCGRP MO required for the Different Transport Paths Based on QoS

Grade feature has been configured in Step 2 and high- and low-quality IP paths have been

configured in Step 3. Ensure that two IP paths are added to different transport resource

groups.

----End

MML Command ExamplesSET GTRANSPARA: LPSCHSW=ENABLE, RATECFGTYPE=SINGLE_RATE;

ADD RSCGRP: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, RU=KBPS,

TXBW=100000, RXBW=100000, TXCBS=120000, TXEBS=120000, TXCIR=80000, RXCIR=80000,

TXPIR=100000, RXPIR=100000, TXPBS=120000;ADD IPPATH: PATHID=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE,

LOCALIP="172.168.1.235", PEERIP="172.169.2.4", PATHTYPE=ANY, DESCRI="ippath 0 for

cn 0";

ADD IPPATH: PATHID=1, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE,LOCALIP="172.168.1.35", PEERIP="172.169.2.4", PATHTYPE=ANY, DESCRI="ippath 0 for

cn 0";

(Set the priorities of the signaling)SET DIFPRI: PRIRULE=DSCP, SIGPRI=48,

OMHIGHPRI=48, OMLOWPRI=14, IPCLKPRI=48;(Set the priorities of differentiated user data)MOD UDT: UDTNO=1, UDTPARAGRPID=40;

(Set the priorities of differentiated user data)MOD UDTPARAGRP: UDTPARAGRPID=40,

PRIRULE=DSCP, PRI=46;ADD IPPATHRT: SRCIP="172.168.1.235", DSTIP="172.169.2.4", TRANRSCTYPE=HQ,

NEXTHOPIP="172.168.0.1";

ADD IPPATHRT: SRCIP="172.168.1.135", DSTIP="172.169.2.4", TRANRSCTYPE=LQ,

NEXTHOPIP="172.168.0.1";

9.5.7 Activation Observation

Note that:

l An S1 tracing task must be created and started on the U2000.

l An IP layer protocol tracing task must be created and started on the U2000.

l The methods used to access a cell and set up a dedicated bearer depend on the type of

UE. For detailed operations, see the user guide provided by the UE manufacturer.

l The methods used to inject UDP packets into the uplink and downlink depend on the

injection tools and data types. User Datagram Protocol (UDP) packet injection is used asan example in this section.

eRAN





93



Transport Resource Configurations and Mapping

Prerequisites

l The cell status is normal.

l The eNodeB works in single-rate mode.

l The QCI of the default bearer for a UE is already determined by the EPC during UE

registration. The following activation observation procedure uses the default bearer with

a QCI of 9 as an example.

Unless there are special requirements, activation observation is performed in single-rate

mode. To set the rate mode for the eNodeB, run the SET GTRANSPARA command.

Procedure

The procedure for activation observation is as follows:

Step 1 Enable a UE to access the cell, with a default bearer set up for the UE. View messages traced

over the S1 interface.

1. Start a tracing task on the U2000 to trace messages over the S1 interface.

2. Enable a UE to access the cell, with a default bearer set up for the UE.

3. View messages over the S1 interface. Transport resource configurations and mapping

take effect if the QoS parameter settings for the bearer whose eRAB-ID is 5 in an

S1AP_INITIAL_CONTEXT_SETUP_REQ message are the same as those in the

network plane, as shown in Figure 9-2.

Figure 9-2 Example of an S1AP_INITIAL_CONTEXT_SETUP_REQ message

Step 2 Start uplink and downlink UDP packet injection to check whether the mapping between

services and transport resources is correct.

1. Run the MOD UDTPARAGRP command to set the activity factor for QCI 9 to 100%.

2. Enable the UE to exit from the E-UTRAN and then access the E-UTRAN, and start

uplink and downlink UDP packet injection at a rate of 5 Mbit/s.

3. Run the LST STANDARDQCI command to check the flow control type for services

with a QCI of 9 and the minimum uplink and downlink guaranteed rates at theapplication layer.

eRAN





94



4. Verify that services with a QCI of 9 are flow-controllable and the minimum uplink and

downlink guaranteed rates are 2 Mbit/s.

5. Run the following commands to view the transport resource mapping and statistics, as

shown in the following example command outputs:

l In link mode, run the DSP IPPATH and DSP RSCGRP commands.

l In endpoint mode, run the DSP RSCGRP command.

Transport resource configurations and mapping take effect if both the following two

conditions are met:

l The non-real-time reserved TX and RX bandwidths are consistent with the minimum

uplink and downlink guaranteed rate for the QCI of 9.

l The non-real-time TX and RX bandwidths are consistent with the actual rate for uplink

and downlink UDP packet injection.

DSP IPPATH:PATHID=0;

%%DSP IPPATH:PATHID=0;%%

RETCODE = 0 Operation succeeded.

DSP IP Path Result

------------------

Path ID = 0

TX Bandwidth(Kbit/s) = 5343 RX Bandwidth(Kbit/s) = 5352

Non-Realtime Reserved TX Bandwidth(Kbit/s) = 2053

Non-Realtime Reserved RX Bandwidth(Kbit/s) = 2053 Realtime TX Bandwidth(Kbit/s) = 0

Realtime RX Bandwidth(Kbit/s) = 0

Non-Realtime TX Bandwidth(Kbit/s) = 5343

Non-Realtime RX Bandwidth(Kbit/s) = 5352 Transport Resource Type = High Quality

IP Path Check Result = Normal

IPMUX Switch Flag = Disable

(Number of results = 1)DSP RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;

%%DSP RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;%%


Display Transmission Resource Group Status

------------------------------------------

Cabinet No. = 0 Subrack No. = 0

Slot No. = 7

Transmission Resource Group Bear Type = IP

Subboard Type = Base Board Bearing Port Type = Ethernet Port

Bearing Port No. = 0

Transmission Resource Group ID = 0

Rate Unit = Kbit/s Realtime TX Bandwidth = 0

Realtime RX Bandwidth = 0

Non-Realtime TX Bandwidth = 5313

Non-Realtime RX Bandwidth = 1058 Non-Realtime Reserved TX Bandwidth = 2106

Non-Realtime Reserved RX Bandwidth = 2106

Tx Bandwidth = 10000 Rx Bandwidth = 10000

Tx Bandwidth Used = NULL

Rx Bandwidth Used = NULL

Tx Bandwidth Usable = NULL Rx Bandwidth Usable = NULL

GBR Tx Bandwidth = 0

GBR Rx Bandwidth = 0

Rate Configuration Type = Single Rate

UL Admission Bandwidth = 10000 DL Admission Bandwidth = 10000

eRAN





95



UL CIR Admission Bandwidth = NULL

DL CIR Admission Bandwidth = NULL UL PIR Admission Bandwidth = NULL

DL PIR Admission Bandwidth = NULL

Realtime Tx Traffic(byte/s) = 674828

(Number of results = 1)

Step 3 Set up a dedicated bearer with a QCI of 3 for the UE to check whether QoS parameters related

to the dedicated bearer take effect as planned.

1. Set up the dedicated bearer with a QCI of 3 for the UE.

2. View the QoS parameters that the bearer setup request contains in an

S1AP_ERAB_SETUP_REQ message. Transport resource configurations and mapping

take effect if the result is consistent with the information shown in Figure 9-3.

Figure 9-3 Example of an S1AP_ERAB_SETUP_REQ message

Step 4 Stop UDP packet injection started in Step 2. Start UDP packet injection on the dedicated

bearer with a QCI of 3. If the bearer configurations and mapping are consistent with the actual

result, transport resource configurations and mapping take effect. Then, start uplink and

downlink UDP packet injection at rates of 1 Mbit/s and 4 Mbit/s, respectively.

If the UDP packet injection rates are consistent with the traffic statistics, as shown in the

following example command outputs, transport resource configurations and mapping take

effect.

Uplink and downlink GBR services are non-flow-controllable, and real-time traffic is

measured by bandwidth.

The rates of uplink and downlink UDP packet injection at the application layer need to be

converted to the bandwidths of transport resource groups at the data link layer. The queried

TX and RX bandwidths are greater than 1 Mbit/s and 4 Mbit/s, respectively.

DSP IPPATH:PATHID=0;O&M #92989

%%DSP IPPATH:PATHID=0;%%


DSP IP Path Result

------------------

Path ID = 0

TX Bandwidth(Kbit/s) = 1064

RX Bandwidth(Kbit/s) = 4256Non-Realtime Reserved TX Bandwidth(Kbit/s) = 2053

eRAN





96



Non-Realtime Reserved RX Bandwidth(Kbit/s) = 2053

Realtime TX Bandwidth(Kbit/s) = 1064 Realtime RX Bandwidth(Kbit/s) = 4256

Non-Realtime TX Bandwidth(Kbit/s) = 0

Non-Realtime RX Bandwidth(Kbit/s) = 0

Transport Resource Type = High Quality

IP Path Check Result = Normal IPMUX Switch Flag = Disable

(Number of results = 1)DSP RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;

%%DSP RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;%%


Display Transmission Resource Group Status

------------------------------------------

Cabinet No. = 0

Subrack No. = 0 Slot No. = 7

Transmission Resource Group Bear Type = IP

Subboard Type = Base Board

Bearing Port Type = Ethernet Port Bearing Port No. = 0

Transmission Resource Group ID = 0

Rate Unit = Kbit/s Realtime TX Bandwidth = 1063

Realtime RX Bandwidth = 4256

Non-Realtime TX Bandwidth = 0

Non-Realtime RX Bandwidth = 0 Non-Realtime Reserved TX Bandwidth = 2053

Non-Realtime Reserved RX Bandwidth = 2053

Tx Bandwidth = 10000

Rx Bandwidth = 10000 Tx Bandwidth Used = NULL

Rx Bandwidth Used = NULL

Tx Bandwidth Usable = NULL

Rx Bandwidth Usable = NULL GBR Tx Bandwidth = 1063

GBR Rx Bandwidth = 4256 Rate Configuration Type = Single Rate UL Admission Bandwidth = 10000

DL Admission Bandwidth = 10000

UL CIR Admission Bandwidth = NULL

DL CIR Admission Bandwidth = NULL UL PIR Admission Bandwidth = NULL

DL PIR Admission Bandwidth = NULL

Realtime Tx Traffic(byte/s) = 664878

(Number of results = 1)

Step 5 Check whether the DSCP in the packet sent from the eNodeB is the same as that is configured

in the DIFPRI and UDTPARAGRP MOs.

1. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace

Management, and then in the navigation tree of the Signaling Trace Management tab page, choose Trace Type > Base Station Device and Transport > Transport Trace >

IP layer protocol trace to create an IP tracing task.

As shown in Figure 9-4, the Type Of Service value for the UDP packet injection with

QCI 3 is 136, and that for the SCTP packet is 184. According to the mapping between

types of services and DSCPs, the DSCPs for the UDP and SCTP packets are 34 (136/4)

and 46 (184/4), respectively.

eRAN





97



Figure 9-4 IP tracing result

2. Run the LST DIFPRI and LST UDTPARAGRP commands to query the DSCPs of the

user data of QCI 3 and signaling.

LST DIFPRI:;

%%LST DIFPRI:;%%


List the Differentiated Service Priority Configuration Data

-----------------------------------------------------------

Priority Rule = DSCP

Signaling Priority = 46 OM High Priority = 18

OM Low Priority = 18

IP Clock Priority = 46(Number of results = 1)

LST UDTPARAGRP:UDTPARAGRPID=42;

%%LST UDTPARAGRP:UDTPARAGRPID=42;%%RETCODE = 0 Operation succeeded.

List User Data Type Parameter Group----------------------------------- User Data Type Transfer Parameter Group ID. = 42

Priority Rule = DSCP

Priority = 34

Act Factor(%) = 100 Primary Transport Resource Type = High Quality

Primary Port Load Threshold(%) = 100

Primary To Secondary Port Load Ratio Threshold(%) = 0(Number of results = 1)

The command output indicates that the DSCPs are the same as those traced in the IP tracing

task. Therefore, the DSCP settings take effect.

----End

Different Transport Paths Based on QoS Grade

Prerequisites

l Scenarios in single-rate mode are as follows:

– The TX or RX bandwidth of transport resource group 0 is 10 Mbit/s. IP path 0 with

high quality joins in transport resource group 0.

– The TX or RX bandwidth of transport resource group 1 is 10 Mbit/s. IP path 1 with

low quality joins in transport resource group 1.

l

Two IP paths (IP path 0 and IP path 1) are added by running the ADD IPPATHRTcommand with their QoS grades set to high and low, respectively.

eRAN





98



l For services with a QCI of 9, set activity factor to 100%, set primary transport resource

type to HQ(High Quality), set primary port load threshold to 30% and set primary-to-

secondary port load ratio threshold to 100% by running the MOD UDTPARAGRP

command.

lThe QCI of the default bearer is 9. The MOD STANDARDQCI command can be usedto set the minimum TX or RX guaranteed rate to 2 Mbit/s for services with a QCI of 9.

Procedure


Step 1 Run the LST DIFPRI command to query the parameters for DiffServ. Then, record the

parameter values.

Step 2 Run the DSP RSCGRP command whether the default bearer joins in the transport resource

group that contains the primary IP path. If so, the Different Transport Paths Based on QoS

Grade feature takes effect.

The following explains why the default bearer should join this group.

The Min_GBR is 2 Mbit/s. The load ratio of the group is: 2/10 x 100% = 20%

This ratio is lower than the primary port load threshold 30%. Therefore, the default bearer

should join the primary group.

Step 3 Run the MOD UDTPARAGRP command to set the primary port load threshold to 10% for

services with a QCI of 9.

MOD UDTPARAGRP: UDTPARAGRPID=48, PRIRULE=DSCP, PRIMPTLOADTH=10;

Step 4 Enable the UE to exit from the E-UTRAN and then access the E-UTRAN. Then, perform

Step 2 and check whether the traffic that requires the Min_GBR on the default bearer is

shared by the secondary IP path 1.

After the UE accesses the cell, the expected result is that the load ratio of the transport

resource group that contains the primary IP path is equal to 20%, which is 10% higher than

the primary port load threshold.

If the results of both this step and Step 2 are as expected, the Different Transport Paths Based

on QoS Grade feature takes effect.

Step 5 Run the MOD UDTPARAGRP command to restore the parameter settings to the values

recorded in Step 1.

MOD UDTPARAGRP: UDTPARAGRPID=48, PRIRULE=DSCP, PRIMPTLOADTH=30;

----End

9.5.8 Reconfiguration

N/A

9.5.9 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on

eNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure for feature deactivation is similar to that for

eRAN





99



feature activation described in "Using the CME to Perform Batch Configuration for

Existing eNodeBs" In the procedure, modify parameters according to Table 9-2.

Table 9-2 Parameters related to transport resource configurations and mapping


Parameter Group Setting Notes

IPPATHRT Base Station

Transport Data or

user-defined sheet

Source IP,

Destination IP,

Transport Resource

Type, Next Hop IP

Remove all routes

for hybrid

transmission.

IPPATH IP Path Cabinet No.,

Subrack No., Slot

No., Subboard Type,

Port No.,IP Path ID, Join

Transport Resource

Group, Transport

Resource Group ID,

Path Type, DSCP,

Local IP, Peer IP,

Transport Resource

Type, Path check,

IPMUX Switch

Flag, Max Subframe

length, Max frame

length, Max Timer,

Description Info

Remove the standby

IP path.

eRAN





100





RSCGRP Base Station

Transport Data or

user-defined sheet

Cabinet No.,

Subrack No., Slot

No., Transport

Resource Group

Bear Type,

Subboard Type,

Bearing Port Type,

Bearing Port No.,

Transport Resource

Group ID, Rate

Unit, Tx Bandwidth,

Rx Bandwidth, TX

Committed BurstSize(Kbit), TX

Excessive Burst

Size(Kbit), Operator

ID, Scheduling

Weight, TX

Committed

Information Rate,

RX Committed

Information Rate,

TX Peak

Information Rate,

RX Peak Information Rate,

TX Peak Burst

Size(Kbit)

Remove the

transport resource

group corresponding

to the standby IP

path.


On the CME, set parameters according to Table 9-2. For detailed instructions, see "Using the

CME to Perform Single Configuration" described for feature activation.

Using MML Commands

l To deactivate Different Transport Paths Based on QoS Grade, perform the following

steps:

Step 1 Run the RMV IPPATHRT command to remove all routes for hybrid transmission.

Step 2 Run the RMV IPPATH command to remove the standby IP path, which has a lower quality.

Step 3 Run the RMV RSCGRP command to remove the transport resource group corresponding to

the standby IP path.

----End

eRAN





101



l To deactivate the function of assigning IP paths to a dedicated transport resource group

in link mode, run the MOD IPPATH command.

l To deactivate the function of assigning user plane data to a dedicated transport resource

group in endpoint mode, run the RMV EP2RSCGRP command.

l No operation can be performed to deactivate transport resource mapping.

MML Command Examples

l Deactivating Different Transport Paths Based on QoS Grade

RMV IPPATHRT: VRFIDX=0, SRCIP="172.168.1.35", DSTIP="172.169.2.4";RMV IPPATH: PATHID=1;

RMV RSCGRP: CN=0, SRN=0, SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0;

l Deactivating the function of assigning IP paths to a dedicated transport resource group in

link mode

MOD IPPATH: PATHID=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, JNRSCGRP=DISABLE;

RMV RSCGRP: CN=0, SRN=0, SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0;

l Deactivating the function of assigning user plane data to a dedicated transport resource

group in endpoint mode

RMV EP2RSCGRP: ENDPOINTID=0, SN=7, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0;

9.6 Deployment of Transport Load Control

9.6.1 Process

None

9.6.2 Requirements


None


None

License

The operator has purchased and activated the license for the feature listed in following table.

Feature ID FeatureName

Model LicenseControl Item

NE Sales Unit

LOFD-0030

11

Enhanced

Transmission

QoS

Management

LT1SETQ

OSM00

Enhanced

Transmission

QoS

Management(F

DD)

eNode

B

per eNodeB

eRAN





102




The parameters for transport load control are all scenario-specific.

Rate Limiting on Physical Ports

The following table describes the parameters that must be set in an LR MO to configure rate

limiting on a physical port, which is the basis of traffic shaping and admission control on this

physical port. This MO cannot be added or removed. It can only be modified.

ParameterName

ParameterID

DataSource

Setting Notes

LR Switch LR . LRSW Network

plan

(negotiati

on notrequired)

Set this parameter based on the network

plan. If admission control on physical ports

is required, this parameter must be set to

ENABLE(Enable) to limit rates on physical ports. When the bandwidth of a transport

network is limited, rate limiting on physical

ports is necessary to prevent network

congestion and packet loss.

UL

Committed

Information

Rate

LR .CIR Network

plan

(negotiati

on not

required)

Set these parameters based on the network

plan. These parameters are valid when LR is

enabled. The LR .CIR parameter is

configured for uplink admission control and

traffic shaping. The LR . DLCIR parameter is

configured for downlink admission control.

It is recommended that LR .CBS be set to 1.5to 2 times the value of LR .CIR.

Committed

Burst Size

LR .CBS Network

plan

(negotiati

on not

required)

Excess Burst

Size

LR . EBS Network

plan

(negotiati

on not

required)

DL

CommittedInformation

Rate

LR . DLCIR Network

plan(negotiati

on not

required)

Admission Control on Transport Resource Groups

The following table describes the parameters that must be set in the TACALG MO to

configure uplink and downlink admission control switches for specified transport resource

groups and admission control thresholds for each QCI. This MO cannot be added or removed.It can only be modified.

eRAN





103



Parameter Name Parameter ID DataSource

Setting Notes

Resource Group Uplink

Admission Control

Algorithm Switch

TACALG. RSCGR

PULCACSWITCH

Network

plan

(negotiati

on not

required)

Set these parameters based

on the network plan. These

parameters specify whether

to enable uplink and

downlink admission control

on transport resource

groups. When the transport

bandwidth is insufficient,

setting these parameters to

ON(On) will enable

admission control over the

uplink and downlink based

on service priorities. The

admission bandwidth for services cannot exceed the

corresponding admission

threshold.

Resource Group

Downlink Admission

Control Algorithm

Switch

TACALG. RSCGR

PDLCACSWITCH

Network

plan

(negotiati

on not

required)

Uplink Handover

Service Admission

Threshold

TACALG.TRMUL

HOCACTH

Network

plan

(negotiati

on not

required)



parameters specify the

uplink and downlink

admission thresholds for

handover services. Their

default values are

recommended.

Downlink Handover

Service Admission

Threshold

TACALG.TRMDL

HOCACTH

Network

plan

(negotiation not

required)

Uplink Golden New

Service Admission

Threshold

TACALG.TRMUL

GOLDCACTH

Network

plan

(negotiati

on not

required)




uplink and downlink


new services, including

gold, silver, and bronze

services. Their default

values are recommended.ARPs are used to distinguish

between gold, silver, and

bronze services.

Downlink Golden New

Service Admission

Threshold

TACALG.TRMDL

GOLDCACTH

Network

plan

(negotiation not

required)

Uplink Silver New

Service Admission

Threshold

TACALG.TRMUL

SILVERCACTH

Network

plan

(negotiati

on not

required)

eRAN





104




Setting Notes

Downlink Silver New

Service Admission

Threshold

TACALG.TRMDL

SILVERCACTH

Network

plan

(negotiati

on not

required)

Uplink Bronze New

Service Admission

Threshold

TACALG.TRMUL

BRONZECACTH

Network

plan

(negotiati

on not

required)

Downlink Bronze New

Service Admission

Threshold

TACALG.TRMDL

BRONZECACTH

Network

plan

(negotiation not

required)

Uplink GBR Service

Admission Threshold

TACALG.TRMUL

GBRCACTH

Network

plan

(negotiati

on not

required)




uplink and downlink


GBR services. Their default

values are recommended.Downlink GBR Service

Admission Threshold

TACALG.TRMDL

GBRCACTH

Network

plan

(negotiation not

required)

Admission Control on Physical Ports


configure admission control switches for physical ports.


Setting Notes

Physical Port Up

Link Admission

Switch

TACALG. PORTULC

ACSW

Network

plan

(negotiati

on not

required)



parameters must be set to

ON(On) when uplink and

downlink admission control

is required over physical

ports.Physical Port Down

Link Admission

Switch

TACALG. PORTDLC

ACSW

Network

plan

(negotiati

on not

required)

eRAN





105



Transport Resource Group Overbooking

The following table describes the parameters that must be set in the TACALG MO used to

configure activation factors for different user types.


Setting Notes

User Data Type

Transfer Parameter

Group ID

UDTPARAGRP.UDT

PARAGRPID

Network

plan

(negotiati

on not

required)


ID of the transport

parameter group

corresponding to a user data

type, which can be set to a

value from 1 to 9 and can be

queried in the UDT MO. Set

this parameter based on the

network plan. Unless

otherwise specified, retainthe default value.

Priority Rule UDTPARAGRP. PRIR

ULE

Network

plan

(negotiati

on not

required)


QoS priority rule. Use the

default value.

Act Factor UDTPARAGRP. ACT

FACTOR

Network

plan

(negotiati

on notrequired)

Set this parameter based on

the network plan. The lower

the parameter value, the

more the admitted services but the more likely that

service bandwidths cannot

be guaranteed.

In eRAN3.0 and later, the

default value of this

parameter for services with

QCIs of 5 to 9 is 0, which

ensures the admission

success rate for non-GBR

services.

Physical Port Overbooking


configure physical port overbooking switches.

eRAN





106




Setting Notes

Physical Port Up

Link OverBooking

Switch

TACALG. PORTULO

BSW

Network

plan

(negotiati

on not

required)


on the network plan. Their

default values are

recommended. When

physical port overbooking is

enabled, the total bandwidth

allocated to resource groups

over a physical port can

exceed the bandwidth

configured for this physical

port. This makes more

efficient use of resources.

Physical Port Down

Link OverBooking

Switch

TACALG. PORTDLO

BSW

Network

plan

(negotiati

on not

required)



configure transport resource preemption switches.


Setting Notes

Uplink Pre-emption

Algorithm Switch

TACALG.TRMULPR

ESW

Network

plan

(negotiation not

required)


on the network plan. By

default, these parameters areset to OFF(Off). Set these

parameters to ON(On) if

uplink and downlink

transport resource

preemption is required.

l When these parameters

are set to ON(On),

transport resource

preemption in the uplink

or downlink may bring

about an increased

admission success rate

for high-priority services

and an increased call

drop rate for low-priority

services.

l When these parameters

are set to OFF(Off),

transport resource

preemption in the uplink

transport bandwidth may

not ensure a high

admission success rate

eRAN





107




Setting Notes

Downlink Pre-

emption Algorithm

Switch

TACALG.TRMDLPR

ESW

Network

plan

(negotiati

on not

required)

for high-priority services,

but this does not increase

the call drop rate for low-

priority services.


The following table describes the parameters that must be set in the TLDRALG MO to

configure transport load reporting thresholds. The system supports load monitoring and load

reporting to the transport load control algorithm and radio interface load balancing algorithm.

This MO cannot be added or removed. It can only be modified. The eNodeB activatestransport load reporting if the radio interface load balancing algorithm exchanges load

information with other eNodeBs.


Setting Notes

Uplink High Load

Trigger Threshold

TLDRALG.TRMULL

DRTRGTH

Network

plan

(negotiati

on not

required)



default values are

recommended. Uplink

transport will enter the

heavy-load state if the proportion of the uplink

transport load to the uplink

transport bandwidth has

remained higher than

TLDRALG.TRMULLDRT

RGTH for a period.

Similarly, downlink


heavy-load state if the

proportion of the downlink

transport load to the

downlink transport bandwidth has remained

higher than

TLDRALG.TRMDLLDRT

RGTH for a period. When

uplink or downlink transport

is in the heavy-load state, the

UL S1 TNL Load Indicator

or DL S1 TNL Load

Indicator sent to neighboring

eNodeBs over the X2

interface is HighLoad.

Downlink High Load

Trigger Threshold

TLDRALG.TRMDLL

DRTRGTH

Network

plan

(negotiati

on not

required)

eRAN





108




Setting Notes

Uplink High Load

Clear Threshold

TLDRALG.TRMULL

DRCLRTH

Network

plan

(negotiati

on not

required)



default values are

recommended. Uplink


medium-load state if the

proportion of the uplink

transport load to the uplink

transport bandwidth has

remained lower than

TLDRALG.TRMULLDRC

LRTH for a period.

Similarly, downlink

transport will enter themedium-load state if the

proportion of the downlink

transport load to the

downlink transport

bandwidth has remained

lower than

TLDRALG.TRMDLLDRC

LRTH for a period. When

uplink or downlink transport

is in the medium-load state,

the UL S1 TNL Load

Indicator or DL S1 TNLLoad Indicator sent to

neighboring eNodeBs over

the X2 interface is

MediumLoad.

Downlink High Load

Clear Threshold

TLDRALG.TRMDLL

DRCLRTH

Network

plan

(negotiati

on not

required)

Uplink Medium

Load Trigger

Threshold

TLDRALG.TRMUL

MLDTRGTH

Network

plan

(negotiati

on not

required)



default values are

recommended.

Downlink Medium

Load Trigger

Threshold

TLDRALG.TRMDL

MLDTRGTH

Network

plan

(negotiati

on not

required)

Uplink Medium

Load Clear

Threshold

TLDRALG.TRMUL

MLDCLRTH

Network

plan

(negotiati

on not

required)

eRAN





109




Setting Notes

Downlink Medium

Load Clear

Threshold

TLDRALG.TRMDL

MLDCLRTH

Network

plan

(negotiati

on not

required)

Transport Resource Overload Control

The following table describes the parameters that must be set in the TOLCALG MO to

configure the transport resources overload algorithm. This MO cannot be added or removed.

It can only be modified.


Setting Notes

Uplink OLC

Arithmetic Switch

TOLCALG.TRMUL

OLCSWITCH

Network

plan

(negotiati

on not

required)


on the network plan. The

recommended value for

them is ON(On).

TOLCALG.TRMULOLCS

WITCH is the switch for

uplink overload control, and

TOLCALG.TRMDLOLCS

WITCH is the switch for downlink overload control.

When the network is

congested due to changes in

the transport bandwidth or

increases in load caused by

non-flow-controllable

services, transport overload

control ensures quality for

high-priority services by

releasing resources of low-

priority services.

Downlink OLC

Arithmetic Switch

TOLCALG.TRMDL

OLCSWITCH

Network

plan

(negotiati

on not

required)

Uplink OLC Trigger

Threshold

TOLCALG.TRMUL

OLCTRIGTH

Network

plan

(negotiati

on not

required)


the network plan. This

parameter specifies the

threshold for triggering

uplink overload control.

When the bandwidth

occupied by uplink services

reaches this threshold, low-

priority services are released

to ensure quality for high-

quality services.

eRAN





110




Setting Notes

Uplink OLC Release

Threshold

TOLCALG.TRMUL

OLCRELTH

Network

plan

(negotiati

on not

required)




threshold for stopping

uplink overload control.

When the bandwidth

occupied by uplink services

falls to this threshold,

services are no longer

released.

Downlink OLC

Trigger Threshold

TOLCALG.TRMDL

OLCTRIGTH

Network

plan

(negotiati

on not

required)




threshold for triggering

downlink overload control.

When the bandwidth

occupied by downlink

services reaches this

threshold, low-priority

services are released to

ensure quality for high-

quality services.

Downlink OLC

Release Threshold

TOLCALG.TRMDL

OLCRELTH

Network

plan

(negotiation not

required)



parameter specifies thethreshold for stopping

downlink overload control.

When the bandwidth

occupied by downlink

services falls to this

threshold, services are no

longer released.

Number of Bearers

Released During

OLC

TOLCALG.TRMOLC

RELBEARERNUM

Network

plan

(negotiati

on notrequired)




number of bearers to bereleased in an overload

control period.

9.6.4 Precautions

It is recommended that you set the ARP of the default bearer to the highest priority during

subscription. It is also recommended that you set the Pre-emption Vulnerability field in the

ARP IE of the ARP to "not pre-emptable". Setting these parameters as recommended enables

eRAN





111



you to avoid call drops due to the release of the default bearer during transport resource

overload.

Set the ARPs of the corresponding EPC NEs as expected before testing admission control,

overload control, or preemption.


N/A

9.6.6 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs



into the Configuration Management Express (CME) for batch configuration. For detailedinstructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for

the eNodeB.





file.



parameters.

All the MOs listed in Table 9-3 except the IPPATH MO require a user-defined template.

Table 9-3 Parameters related to transport load control



LR Base Station

Transport Data or

user-defined sheet

Cabinet No., Subrack No.,

Slot No., Subboard Type, Port

Type, Port No, LR Switch,

UL Committed InformationRate(Kbit/s), Committed

Burst Size(Kbit), Excess

Burst Size(Kbit), DL

Committed Information

Rate(Kbit/s)

The summary data

file needs to be

customized based on

the template namedEn_Basic_eRAN_S

haring_Link.

eRAN





112





TACALG Base Station

Transport Data or

user-defined sheet

Resource Group Uplink

Admission Control Algorithm

Switch, Resource Group

Downlink Admission Control

Algorithm Switch, Uplink

Handover Service Admission

Threshold(%), Downlink

Handover Service Admission

Threshold(%), Uplink Golden

New Service Admission


Golden New Service

Admission Threshold(%),Uplink Silver New Service

Admission Threshold(%),

Downlink Silver New Service


Uplink Bronze New Service


Downlink Bronze New

Service Admission

Threshold(%), Uplink GBR

Service Admission


GBR Service AdmissionThreshold(%), Uplink Pre-

emption Algorithm Switch,

Downlink Pre-emption

Algorithm Switch, Physical

Port Up Link OverBooking

Switch, Physical Port Down

Link OverBooking Switch,

Physical Port Up Link

Admission Switch, Physical

Port Down Link Admission

Switch, Emergency Call

Preferential AdmissionSwitch

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_S

haring_Link.

eRAN





113





TLDRALG Base Station

Transport Data or

user-defined sheet

Uplink High Load Trigger


High Load Trigger

Threshold(%), Uplink High

Load Clear Threshold(%),

Downlink High Load Clear

Threshold(%), Uplink

Medium Load Trigger


Medium Load Trigger

Threshold(%), Uplink

Medium Load Clear

Threshold(%), Downlink Medium Load Clear

Threshold(%)

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_S

haring_Link.

TOLCALG Base Station

Transport Data or

user-defined sheet

Uplink OLC Arithmetic

Switch, Downlink OLC

Arithmetic Switch, Uplink

OLC Trigger Threshold(%),

Uplink OLC Release

Threshold(%), OLC Release

Bearer No., Downlink OLC

Trigger Threshold(%),

Downlink OLC ReleaseThreshold(%)

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_S

haring_Link.

IPPATH IP Path Cabinet No., Subrack No.,

Slot No., Subboard Type, Port

No.,

IP Path ID, Join Transport

Resource Group, Transport

Resource Group ID, Path

Type, DSCP, Local IP, Peer

IP, Transport Resource Type,

Path check, IPMUX Switch

Flag, Max Subframe length,Max frame length, Max

Timer, Description Info

-





Step 1 Customize a summary data file with the MOs and parameters listed in section "Using theCME to Perform Batch Configuration for Newly Deployed eNodeBs". For online help, press

eRAN





114







Configuration Data (U2000 client mode), or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB

data stored on the CME into the customized summary data file.











----End




Step 1 In the planned data area, click Base Station in the upper left corner of the configurationwindow.


eRAN





115





Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are

displayed in area 4.





----End

Using MML Commands

Transport load control involves configuring the following functions:

l LR on Physical Ports

Run the SET LR command to configure LR on physical ports.

This configuration is used for traffic shaping and admission control on physical ports. It also

impacts bandwidth allocation of transport resources.

l Admission Control on Transport Resource Groups

Run the SET TACALG command to configure admission control on transport resource

groups by setting the uplink or downlink admission switch and threshold.

l Admission Control on Physical Ports

Run the SET TACALG command to enable admission control on physical ports.

eRAN





116



Both LR and TACALG MOs need to be configured. If the two MOs are not configured,

configure them by referring to LR on Physical Ports and Admission Control on

Transport... in this section.

l Transport Resource Group Overbooking

Step 1 Run the LST UDT command to query the ID of the transport parameter group corresponding


Step 2 Run the MOD UDTPARAGRP command to configure transport resource group overbooking

by setting activity factors of the user data. Note that these factors will be included in

calculations of the bandwidth to be requested.

----End

l Physical Port Overbooking

Run the SET TACALG command to configure physical port overbooking.

Physical port overbooking works properly only when the sum of the bandwidths of transport

resource groups on a physical port is greater than the bandwidth of this physical port.

l Transport Resource Preemption

Run the SET TACALG command to enable transport resource preemption.

This function is triggered if admission fails on a physical port or transport resource groups on

this physical port. For this case, assume that admission control on the physical ports and

transport resource groups has been enabled.

l Load Reporting

Run the SET TLDRALG command to configure thresholds for entering medium-load andheavy-load states. Unless there are special requirements, retain the default values. Note that

the load status is always reported, and therefore enabling the switch for load reporting is not

required.

l Transport Overload Control

Run the SET TOLCALG command to turn on the overload control switch and set the

thresholds for triggering and releasing overload control.


l LR on Physical Ports

SET LR: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=100000, CBS=200000,

EBS=150000;

l Admission Control on Transport Resource Groups

SET TACALG: RSCGRPULCACSWITCH=ON, RSCGRPDLCACSWITCH=ON, TRMULHOCACTH=95,TRMDLHOCACTH=95, TRMULGOLDCACTH=90, TRMDLGOLDCACTH=90, TRMULSILVERCACTH=85,

TRMDLSILVERCACTH=85, TRMULBRONZECACTH=85, TRMDLBRONZECACTH=85, TRMULGBRCACTH=80,

TRMDLGBRCACTH=80;

l Admission Control on Physical Ports

SET TACALG: PORTULCACSW=ON, PORTDLCACSW=ON;

l Transport Resource Group Overbooking

LST UDT;

MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, ACTFACTOR=60;MOD UDTPARAGRP: UDTPARAGRPID=48, PRIRULE=DSCP, ACTFACTOR=60;

eRAN





117



l Physical Port Overbooking

SET TACALG: PORTULOBSW=ON, PORTDLOBSW=ON;

l Transport Resource Preemption

SET TACALG: TRMULPRESW=ON, TRMDLPRESW=ON;

l Load Reporting

SET TLDRALG: TRMULLDRTRGTH=70, TRMDLLDRTRGTH=70, TRMULLDRCLRTH=65,

TRMDLLDRCLRTH=65, TRMULMLDTRGTH=50, TRMDLMLDTRGTH=50, TRMULMLDCLRTH=45,TRMDLMLDCLRTH=45;

l Transport Overload Control

SET TOLCALG: TRMULOLCSWITCH=ON, TRMDLOLCSWITCH=ON, TRMULOLCTRIGTH=95,

TRMULOLCRELTH=90, TRMDLOLCTRIGTH=95, TRMDLOLCRELTH=90, TRMOLCRELBEARERNUM=2;


Note that:


l The methods used to access a cell and set up a dedicated bearer depend on the type of

UE. For detailed operations, see the user guide provided by the UE manufacturer.


injection tools and data types. User Datagram Protocol (UDP) packet injection is used as

an example in this section.

NOTE

Anonymization has been performed on S1 interface tracing tasks, and therefore no security risk exists.

Admission Control on Transport Resource GroupsThe procedure for activation observation is as follows:

Step 1 Run the DSP CELL command. If Cell instance state is Normal, the cell status is normal.

Step 2 Run the LST TACALG command. If Resource Group Uplink Admission Control

Algorithm Switch and Resource Group Downlink Admission Control Algorithm Switch

are On, transport admission control is enabled. Then, record all service admission thresholds.

Step 3 Run the SET TACALG command to set the thresholds for gold, silver, and bronze services to

0, and run the MOD UDTPARAGRP command to change the activity factor of the default

bearer to 100%.

Step 4 Start an S1 interface tracing task, and enable a UE to access the cell. If the UE cannot access

the cell, admission control on transport resource groups takes effect.

Step 5 Verify that the S1AP_INITIAL_CONTEXT_SETUP_FAIL message contains the cause value

"transport---transportresource- unavailable."

Step 6 Run the SET TACALG command to set Resource Group Uplink Admission Control

Algorithm Switch and Resource Group Downlink Admission Control Algorithm Switch

to OFF(Off). Alternatively, set admission thresholds for gold, silver, and bronze services, or

retain the default admission thresholds.

Step 7 Perform Step 4 to enable the UE to access the cell. If the result is as expected, admissioncontrol on transport resource groups takes effect.

eRAN





118



Step 8 Run the SET TACALG command to restore the parameter settings to the values recorded in

Step 2.

----End

Admission Control on Physical Ports


Step 1 Run the SET TACALG command to set Resource Group Uplink Admission Control

Algorithm Switch or Resource Group Downlink Admission Control Algorithm Switch to

OFF(Off).

Step 2 Run the LST TACALG command.

If Physical Port Up Link Admission Switch and Physical Port Down Link Admission

Switch parameters are On, admission control on physical ports is enabled. To simplify

activation observation, you are advised to set Physical Port Up Link OverBooking Switchand Physical Port Down Link OverBooking Switch to ON(On).

The transport resource group admission algorithm takes effect preferentially, which affects the

verification of the physical port admission algorithm.

Step 3 Run the LST LR command. If LR Switch is Enable, the LR function is enabled. Then,

record the limited bandwidth value.

Step 4 Start an S1 interface tracing task, and enable a UE to access the cell. View the QCI of the

default bearer in an S1AP_INITIAL_CONTEXT_SETUP_REQ message.

Step 5 Run the LST STANDARDQCI command to query the minimum uplink and downlink

guaranteed rates and record them. Run the MOD UDTPARAGRP command to change theactivity factor of the default bearer to 100%.

Step 6 Run the SET LR or MOD STANDARDQCI command. Ensure that the values of the

StandardQci.UlMinGbr and StandardQci. DlMinGbr parameters in the STANDARDQCI

MO are greater than the values of the LR .CIR and LR . DLCIR parameters in an LR MO,

respectively.

Step 7 Enable the UE to access the cell. If the access fails and the

S1AP_INITIAL_CONTEXT_SETUP_FAIL message traced over the S1 interface contains

the cause value "transport---transportresource- unavailable", admission control on physical

ports takes effect.

Step 8 Run the SET LR or MOD STANDARDQCI command to restore the configurations of theLR and STANDARDQCI MOs.

Step 9 Enable the UE to access the cell again. If the results in Step 7 and this step are as expected,

admission control on physical ports takes effect.

----End

Transport Resource Group Overbooking


Step 1 Start an S1 interface tracing task, and enable a UE to access the cell. View the QCI of thedefault bearer in an S1AP_INITIAL_CONTEXT_SETUP_REQ message.

eRAN





119



Step 2 Run the LST STANDARDQCI command to query the minimum uplink and downlink

guaranteed rates corresponding to the QCI of the default bearer.

Step 3 Run the LST UDTPARAGRP command to query the activity factor corresponding to the

QCI of the default bearer. Then, record the value.

Step 4 Run the MOD UDTPARAGRP command to set the activity factor to 50% corresponding to

the QCI of the default bearer.

Step 5 Enable the UE to access the cell again and run the DSP IPPATH command to query the

admission bandwidth of the default bearer. If the non-real-time reserved TX and RX

bandwidths are half of the minimum uplink and downlink guaranteed rates queried in Step 2,

respectively, transport resource group overbooking takes effect.

Step 6 Restore the setting of the activity factor to the value recorded in Step 3.

----End

Physical Port Overbooking


Step 1 Run the LST TACALG command. If Physical Port Up Link OverBooking Switch and

Physical Port Down Link OverBooking Switch are On, uplink and downlink physical port

overbooking are enabled.

Step 2 Run the LST RSCGRP command to query the bandwidths configured for the transport

resource group. Then, record the values.

Step 3 Run the LST GTRANSPARA command to check the rate mode of the eNodeB.

Step 4 Run the LST LR command to check whether LR Switch is set to Enable. If the value isEnable, record the limited bandwidths. If the value is not Enable, go to the next step.

Step 5 Run the SET LR command to set LR Switch to ENABLE(Enable) and set UL Committed

Information Rate and DL Committed Information Rate to their minimum values. With

such settings, the uplink and downlink committed bandwidths of the physical port are

respectively lower than the total TX and RX bandwidths of the transport resource groups on

the physical port.

Step 6 Run the DSP RSCGRP command to query the admission bandwidths of the transport

resource group. If the values are consistent with the bandwidth values queried in Step 2,

physical port overbooking takes effect.

l In single-rate mode, query UL Admission Bandwidth and DL Admission Bandwidth.

l In dual-rate mode, query UL CIR Admission Bandwidth, DL CIR Admission

Bandwidth, UL PIR Admission Bandwidth, and DL PIR Admission Bandwidth.

Step 7 Run the SET TACALG command with Physical Port Up Link OverBooking Switch and

Physical Port Down Link OverBooking Switch set to OFF(Off).

Step 8 Repeat Step 6 to verify that the admission bandwidths of the transport resource group are

inconsistent with the bandwidths queried in Step 2.

Physical port overbooking has been disabled previously. Either in the uplink or downlink, if

the total bandwidth configured for the transport resource groups on the physical port is greater

than the limited bandwidth, the admission bandwidth is allocated based on the configured bandwidth and the resource group scheduling weight. The limited bandwidth has been set to

eRAN





120



the minimum value in Step 5. Therefore, the admission bandwidth of a transport resource

group is much lower than the configured bandwidth; the admission bandwidth may be zero.

Step 9 Run the SET LR command to restore the parameter settings to the values recorded in Step 4.

----End


Before verifying the transport resource preemption feature, query and set QoS parameters on

the EPC.

You can check the S1AP_INITIAL_CONTEXT_SETUP_REQ and

S1AP_ERAB_SETUP_REQ messages traced over the S1 interface for EPC-delivered QoS

parameters, as shown in Figure 9-6 and Figure 9-7.

Figure 9-6 Example of an S1AP_INITIAL_CONTEXT_SETUP_REQ message

eRAN





121



Figure 9-7 Example of an S1AP_ERAB_SETUP_REQ message

NOTE

As shown in Figure 9-6 and Figure 9-7, the priorityLevel, pre-emptionCapability, and pre-

emptionVulnerability fields indicate the ARP, preemption capability, and preemption vulnerability for a

specific QCI, respectively. Check the parameter setting definitions with EPC maintenance engineers, as

the definitions of the parameter settings vary depending on EPCs. For example, according to parameter

setting definitions in Huawei EPCs, the value 1 for pre-emptionCapability means that services with the

specific QCI can trigger preemption and the value 0 means the opposite. In addition, the value 1 for pre-

emptionVulnerability means being preemptable and the value 0 means the opposite.

Prerequisites

l The default bearer carries services with a QCI of 9. This bearer cannot be preempted.

Otherwise, the UE may experience service drops.

l If the values of the priorityLevel, pre-emptionCapability, and pre-emptionVulnerability

fields are 1, 0, and 0, respectively, this bearer is not preemptable. If this bearer is

preemptable, confirm that its ARP is high enough to prevent this bearer from being

preempted.

l For the dedicated bearer with a QCI of 2, the values of the priorityLevel, pre-

emptionCapability, and pre-emptionVulnerability fields are 10, 1, and 1, respectively.

That is, this bearer can preempt lower-priority bearers and be preempted by higher-

priority bearers.



That is, this bearer cannot preempt lower-priority bearers but can be preempted by

higher-priority bearers.



That is, this bearer can neither preempt lower-priority bearers nor be preempted by

higher-priority bearers.

l The committed bandwidth of a physical port is greater than the sum of the bandwidths of

all transport resource groups on this port so that the bandwidths configured for eachgroup are the same as the actual admission bandwidths.

eRAN





122



Procedure


Step 1 Run the LST TACALG command to check switch settings. Then, record the values.

If Resource Group Uplink Admission Control Algorithm Switch and Resource Group

Downlink Admission Control Algorithm Switch are On, transport admission control is

enabled. If Uplink Pre-emption Algorithm Switch and Downlink Pre-emption Algorithm

Switch are On, transport resource preemption is enabled.

Transport resource preemption is activated only after both admission control and preemption

switches are turned on. To turn on these switches, run the SET TACALG command. In

addition, run the MOD UDTPARAGRP command to set the activity factors for QCI 2, QCI

7, QCI 8, and QCI 9 to 100%.

Step 2 Run the DSP RSCGRP command to query the admission bandwidths of the transport

resource group. Then, record the values.

Step 3 Run the MOD RSCGRP command to set the TX and RX bandwidths to 10 Mbit/s for the

transport resource group.

l In single-rate mode, set the Tx Bandwidth and Rx Bandwidth parameters.

l In dual-rate mode, set the TX Committed Information Rate, RX Committed

Information Rate, RX Peak Information Rate, and TX Peak Burst Size parameters.

The single-rate mode is used in this procedure as an example.

Step 4 Run the SET TACALG command to set the admission thresholds for new gold, silver, and

bronze services to 80%.

Step 5 Run the LST STANDARDQCI command to check Min_GBR settings. Then, record the

values.

Step 6 Run the MOD STANDARDQCI command to set the uplink or downlink Min_GBR to 4

Mbit/s for services with QCIs of 7 and 8 and to 2 Mbit/s for services with a QCI of 9.

NOTE

The rates at the application layer need to be converted into the bandwidths of transport resource groups

at the data link layer for admission control. In this example, the application-layer rates substitute data-

link-layer rates for simplicity.

Step 7 Start S1 interface tracing for the eNodeB.

The tracing result shows that the UE accesses the cell, with the default bearer successfully

admitted to the transport resource group.

Step 8 Use a UE to set up a flow-controllable dedicated bearer with a QCI of 7.

As indicated in the S1AP_ERAB_SETUP_REQ and S1AP_ERAB_SETUP_RSP messages,

the bearer is successfully set up.

Step 9 Operate the UE to set up a non-flow-controllable dedicated bearer with a QCI of 2 and an

uplink or downlink GBR of 3 Mbit/s.

The total requested load proportion is calculated as follows: (2 x 100% + 4 x 100% + 3)/10 =

90%. It exceeds the admission threshold 80%. Therefore, the service with a QCI of 2 cannot

be admitted, and a preemption procedure is triggered. In the S1 interface tracing result, the

S1AP_ERAB_REL_IND message indicates that the bearer for the service with a QCI of 7 isreleased as expected. The preemption algorithm takes effect.

eRAN





123



Step 10 Run the SET TACALG command with the Uplink Pre-emption Algorithm Switch and

Downlink Pre-emption Algorithm Switch parameters set to OFF(Off).

Step 11 Enable the UE to access the cell again, and perform Step 7, Step 8 and Step 9. Check whether

the bearer for the service with a QCI of 2 can be successfully set up.

When the preemption switch is turned off, this bearer cannot be set up because of an

admission failure. If the result is as expected, transport resource preemption takes effect.

Step 12 Enable the UE to access the cell again. Then, perform Step 7 and Step 8, with QCI 7 changed

to QCI 8.

Step 13 Perform Step 9. to check services with a QCI of 2.

The expected result is that services with a QCI of 2 are not admitted because the Pre-emption

Vulnerability field for services with a QCI of 8 is set to "not pre-emptable".

Step 14 Run the MOD RSCGRP, SET TACALG, and MOD UDTPARAGRP commands to restore

the parameter settings.

----End


Transport load reporting is activated by default. There is no need to verify it.

Overload Control by Traffic Licenses

Overload control by traffic licenses is activated by default, and parameters such as thresholds

retain their default values. Therefore, there is no need to verify it.

Transport Overload Control

Prerequisites

Prerequisite assumption for transport overload control is the same as that for transport

resource preemption. Assume that transport admission control is already enabled to simulate

situations on live networks.

Procedure

Activation observation method for transport overload control over the S1 interface:

Step 1 Run the LST TACALG command to check switch settings. Then, record the values.

If Resource Group Uplink Admission Control Algorithm Switch and Resource Group

Downlink Admission Control Algorithm Switch are On, transport admission control is

enabled. To turn on these switches, run the SET TACALG command. In addition, run the

MOD UDTPARAGRP command to set the activity factors for QCI 2, QCI 7, and QCI 9 to

100%.

Step 2 Run the LST TOLCALG command to check switch settings and the values of Uplink OLC

Trigger Threshold(%) and Uplink OLC Release Threshold(%). Then, record the switch

settings and thresholds.

If Uplink OLC Arithmetic Switch and Downlink OLC Arithmetic Switch are On,

transport overload control is activated. In this example, the values of Uplink OLC TriggerThreshold(%) and Uplink OLC Release Threshold(%) are 85 and 65, respectively.

eRAN





124



Step 3 Run the DSP RSCGRP command to check the uplink or downlink admission bandwidths of a

transport resource group. Then, record the values.

Step 4 Run the MOD RSCGRP command to set the TX and RX bandwidths to 10 Mbit/s for the


l In single-rate mode, set the Tx Bandwidth and Rx Bandwidth parameters.

l In dual-rate mode, set the TX Committed Information Rate, RX Committed

Information Rate, RX Peak Information Rate, and TX Peak Burst Size parameters.

The single-rate mode is used in this procedure as an example.

Step 5 Run the SET TACALG command to set the admission thresholds for new gold, silver, and

bronze services to 90%.

Step 6 Run the LST STANDARDQCI command to check Min_GBR settings. Then, record the

values.

Step 7 Run the MOD STANDARDQCI command to set the uplink or downlink Min_GBR to 4Mbit/s for services with a QCI of 7 and to 2 Mbit/s for services with a QCI of 9.

NOTE

The rates at the application layer need to be converted into the bandwidths of transport resource groups

at the data link layer for admission control. In this example, the application-layer rates substitute data-

link-layer rates for simplicity.

Step 8 Start S1 interface tracing on the eNodeB.

The tracing result shows that the UE accesses the cell, with the default bearer successfully

admitted to the transport resource group.

Step 9 Use a UE to set up a flow-controllable dedicated bearer with a QCI of 7.

As indicated in the S1AP_ERAB_SETUP_REQ and S1AP_ERAB_SETUP_RSP messages,

the bearer is successfully set up.

Step 10 Operate the UE to set up a non-flow-controllable dedicated bearer with a QCI of 2 and an

uplink or downlink GBR of 2 Mbit/s. Start uplink UDP packet injection at 2 Mbit/s.

The total load proportion is calculated as follows: (2 + 4 + 2)/10 = 80%. It is lower than the

admission threshold for new services and the threshold for triggering uplink overload control.

Therefore, this service is admitted successfully and not released.

Step 11 Run the MOD RSCGRP command to change the TX and RX bandwidths of the transport

resource group to 5 Mbit/s.

Step 12 Check the S1AP_ERAB_REL_IND message traced over the S1 interface for bearer release.

If the message indicates that the bearers for the services with QCIs of 7 and 2 are released,

transport overload control takes effect.

Step 13 Run the SET TOLCALG command with the Uplink OLC Arithmetic Switch and

Downlink OLC Arithmetic Switch parameters set to OFF(Off).

Step 14 Enable the UE to access the cell again and perform Step 9 through Step 12. Check whether

the bearers for the services with QCIs of 2 and 7 are released.

When overload control is deactivated, the bearers are not released even when overload occurs.

eRAN





125



Step 15 Run the MOD RSCGRP, MOD STANDARDQCI, SET TOLCALG, MOD

UDTPARAGRP and SET TACALG commands to restore the parameter settings.

----End

Activation observation method for transport overload control over the eX2 interface:

Step 1 Add the eX2 interface between two eNodeBs and configure the Carrier Aggregation or UL

CoMP feature. For details about how to configure the feature, see eRAN Carrier Aggregation

Feature Parameter Description or eRAN UL CoMP Feature Parameter Description.

Step 2 Start eX2 interface tracing on the eNodeB.

Step 3 Run the MOD RSCGRP command to manually produce a transport link overload. For

example, set Tx Bandwidth or Rx Bandwidth to 35000.

MOD RSCGRP: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RU=KBPS,

TXBW=35000, RXBW=35000;

Step 4 Observe the messages traced over the eX2 interface. The tracing result shows that the eX2-Ulink has been deleted.

----End


N/A

9.6.9 Deactivation

Using the CME to Perform Batch ConfigurationBatch reconfiguration using the CME is the recommended method to deactivate a feature on

eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple

eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for


Existing eNodeBs." In the procedure, modify parameters according to Table 9-4.

eRAN





126



Table 9-4 Parameters related to transport load control



TACALG Base Station

Transport Data or

user-defined sheet

RSCGRPULCACS

WITCH,

RSCGRPDLCACS

WITCH,

PORTULCACSW,

PORTDLCACSW,

PORTULOBSW,

PORTDLOBSW,

TRMULPRESW,

TRMDLPRESW

Set the following

parameters to

OFF(Off):

l RSCGRPULCA

CSWITCH

l RSCGRPDLCA

CSWITCHPORT

ULCACSW

l PORTDLCACS

W

l PORTULOBSW

and

PORTDLOBSW

l TRMULPRESW

l TRMDLPRESW


Transport Data or

user-defined sheet

ACTFACTOR Set this parameter to

100.

TOLCALG Base Station

Transport Data or user-defined sheet

TRMULOLCSWIT

CH,TRMDLOLCSWIT

CH

Set the following

parameters toOFF(Off):

l TRMULOLCSW

ITCH

l TRMDLOLCSW

ITCH


On the CME, set parameters according to Table 9-4. For detailed instructions, see "Using theCME to Perform Single Configuration."

Using MML Commands

l To deactivate admission control on transport resource groups, run the SET TACALG

command to turn off the Resource Group Uplink Admission Control Algorithm

Switch and Resource Group Downlink Admission Control Algorithm Switch.

l To deactivate admission control on physical ports, run the SET TACALG command to

turn off the Physical Port Up Link Admission Switch and Physical Port Down Link

Admission Switch.

l To deactivate transport resource group overbooking, perform the following steps:

eRAN





127





Step 2 Run the MOD UDTPARAGRP command to set Act Factor to 100 (activity factor: 100%),

indicating that transport resource group overbooking is disabled.

----End

l To deactivate physical port overbooking, run the SET TACALG command to turn off

the Physical Port Up Link OverBooking Switch and Physical Port Down Link

OverBooking Switch.

l To deactivate transport resource preemption, run the SET TACALG command to turn

off the Uplink Pre-emption Algorithm Switch and Downlink Pre-emption Algorithm

Switch.

l No operation can be performed to disable transport load reporting.

l To deactivate transport overload control, run the SET TOLCALG command to turn off

the Uplink OLC Algorithm Switch and Downlink OLC Algorithm Switch.


l Deactivating admission control on transport resource groups

SET TACALG: RSCGRPULCACSWITCH=OFF, RSCGRPDLCACSWITCH=OFF;

l Deactivating admission control on physical ports

SET TACALG: PORTULCACSW=OFF, PORTDLCACSW=OFF;

l Deactivating transport resource group overbooking

MOD UDTPARAGRP: UDTPARAGRPID=48, PRIRULE=DSCP, ACTFACTOR=100;

l Deactivating physical port overbooking

SET TACALG: PORTULOBSW=OFF, PORTDLOBSW=OFF;

l Deactivating transport resource preemption

SET TACALG: TRMULPRESW=OFF, TRMDLPRESW=OFF;

l Deactivating transport overload control

SET TOLCALG: TRMULOLCSWITCH=OFF, TRMDLOLCSWITCH=OFF;

9.7 Deployment of Transport Congestion Control

9.7.1 Process

None

9.7.2 Requirements


As a Huawei proprietary function, IP PM requires that the EPC equipment be provided by

Huawei and support IP PM. For details about whether an EPC equipment version supports IP

PM, contact Huawei EPC engineers.


None

eRAN





128



License

Operators must purchase and activate the following license.

Feature ID Feature Name Model License

Control Item

NE Sales Unit

LOFD-003012 IP Performance

Monitoring

LT1S0I

PAPM0

0

IP Performance

Monitoring

eNod

eB

per eNodeB

LOFD-003011 Enhanced

Transmission

QoS

Management(FD

D)

LT1SET

QOSM0

0

Enhanced

Transmission

QoS

Management(F

DD)

eNod

eB

per eNodeB


The parameters for transport congestion control are all scenario-specific.


The MOs related to transport differentiated flow control are RSCGRP, RSCGRPALG, LR ,

PRI2QUE and STANDARDQCI.

Traffic Shaping Switch

The following table describes the parameters that must be set in an RSCGRPALG MO to

configure the traffic shaping switch for a transport resource group. Parameter settings in this

MO are automatically generated after the RSCGRP MO is configured. Before changing

parameter settings in this MO, ensure the RSCGRP MO is already configured.

eRAN





129




TX Traffic Shaping

Switch

RSCGRPALG.TXS

SW

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

The recommended

value is ON(On).

l Set this

parameter to

ON(On) if traffic

shaping based on

the TX

bandwidth is

required. This

ensures that the

TX traffic does

not exceed the

capability of

downstream

routers and

prevents packet

discarding and

network

congestion.

l If this parameter

is set to ON(On),

the TX rate of

the resourcegroup cannot

exceed the uplink

admission

bandwidth or

uplink PIR

admission

bandwidth,

preventing

network

congestion and

ensuring service

quality.

l If this parameter

is set to

OFF(Off), the

TX rate of the

resource group

may exceed the

TX bandwidth

configured for it.

In this case,

network

congestion may

eRAN





130




occur and service

quality may be

degraded.

Rate Limiting on a Physical Port

Collect parameters in an LR MO used to configure rate limiting on a physical port to achieve

traffic shaping on this physical port. For details about data preparation for the LR MO, see

9.6.3 Data Preparation.

Scheduling of Transport Resource Group Queues

The following table describes the parameters that must be set in the PRI2QUE MO to

configure the mapping between QoS priorities (only DSCPs are currently supported) and

internal queues. This MO cannot be added or removed. It can only be modified. The

associated MO is UDTPARAGRP. The UDTPARAGRP MO specifies the mapping from

QCIs to DSCP values, and the PRI2QUE MO specifies the mapping from DSCP values to

internal queues.


PriOfQue0 PRI2QUE. PRI0 Network plan

(negotiation not

required)

Set these parameters

based on the

network plan.

These parameters

specify the DSCP

priorities of the

queues. Their

default values are

recommended.




(negotiation not

required)


(negotiation not

required)


(negotiation not

required)


(negotiation not

required)


(negotiation not

required)

The DSCP of queue 7 is always 0. Service packets with DSCPs lower than PRI2QUE. PRI6 are all assigned to queue 7.

eRAN





131



Back-Pressure Algorithm


turn on the back-pressure switch and configure related parameters. The eNodeB performs

operations such as back-pressure based on the parameter settings in the RSCGRPALG.


Traffic Control

Switch

RSCGRPALG.TCS

W

Network plan

(negotiation not

required)

Set this parameter

based on the

network plan.

This parameter

specifies whether to

enable the back-

pressure algorithm.

This algorithm

prevents packet loss

caused by network congestion. By

default, this

algorithm is enabled.


recommended.

Congestion Time

Threshold

RSCGRPALG.CTT

H

Network plan

(negotiation not

required)


based on the

network plan.

Retain their default

values unless there

are special

requirements. The

RSCGRPALG MO,

RSCGRPALG.CCT

TH value must be

less than the

RSCGRPALG.CTT

H value.

Congestion Clear

Time Threshold

RSCGRPALG.CCT

TH

Network plan


TX Bandwidth

Adjust Minimum

RSCGRPALG .TX

BWAMIN

Network plan

(negotiation not

required)


based on the

network plan. If the

parameters are set to

small values and

available bandwidth

for the transport

resource group

decreases due to

congestion, the

transmission

admission may fail.

RX Bandwidth

Adjust Minimum

RSCGRPALG . RX

BWAMIN

Network plan

(negotiation not

required)

eRAN





132




MOs related to transport dynamic flow control are RSCGRPALG, IPPMSESSION,

eNodeBPath and IPPATH. Dynamic flow control dynamically adjusts the bandwidth

configured in the RSCGRP MO based on the QoS parameters in the IPPMSESSION MO

and the thresholds configured in the RSCGRPALG MO.

Dynamic Flow Control Switch


turn on the dynamic flow control switch and configure related thresholds. This MO cannot be

added or removed. It can only be modified.

ParameterName

ParameterID


TX Traffic

Shaping

Switch

RSCGRPA

LG.TXSSW

Network plan

(negotiation

not required)

This parameter specifies whether to

enable TX traffic shaping. It is

recommended that TX traffic shaping be

enabled. Set this parameter to ON(On) if

dynamic transport flow control is

required.

l If this parameter is set to ON(On), the

TX rate of the resource group cannot

exceed the uplink admission

bandwidth or uplink PIR admission

bandwidth, preventing network

congestion and ensuring service

quality.

l If this parameter is set to OFF(Off),

the TX rate of the resource group can

exceed the uplink admission

bandwidth or uplink PIR admission

bandwidth, probably causing network

congestion and compromising service

quality.

TX

Bandwidth

Adjustment

Switch

RSCGRPA

LG.TXBWA

SW

Network plan

(negotiation

not required)


plan.

Set this parameter to ON(On) if uplink

transport dynamic flow control is

required.

RX

Bandwidth

Adjustment

Switch

RSCGRPA

LG. RXBWA

SW

Network plan

(negotiation

not required)


plan.

Set this parameter to ON(On) if the

downlink admission bandwidth needs to

be adjusted for the resource group. In this

case, downlink dynamic flow control also

needs to be enabled on the EPC.

eRAN





133



ParameterName

ParameterID


Packet Loss

Ratio Down

Threshold

RSCGRPA

LG. PLRDT

H

Network plan

(negotiation

not required)

A small value of either parameter enables

the eNodeB to respond to transport

network congestion more quickly and

therefore promptly adjust the bandwidth.

However, this makes the eNodeB more

prone to delay variation on the transport

network and therefore decreases network

robustness. Retain the default values for

these parameters.

Delay Down

Threshold

RSCGRPA

LG. DDTH

Network plan

(negotiation

not required)

IP PM Session

The following table describes the parameters that must be set in an IPPMSESSION MO to

configure an IP PM session. This session is used to monitor the link transmission quality of an

IP path. For details, see IP Performance Monitor Feature Parameter Description.

IP Path Application Type

The following table describes the parameters that must be set in an IPPATH MO to

implement differentiated service transmission.

ParameterName

ParameterID

DataSource

Setting Notes

IP path ID IPPATH. Pat hId

Network plan(negotiation

not required)

Indicates the IP of an IP path.

Local IP IPPATH.

LocalIP

Network plan

(negotiation

not required)

Indicates the local IP address of an IP

path.

Peer IP IPPATH.

PeerIP

Network plan

(negotiation

not required)

Indicates the peer IP address of an IP path.

Path Type IPPATH.

PathType

Network plan

(negotiationnot required)

Indicates the type of an IP path.

DSCP IPPATH.

DSCP

Network plan

(negotiation

not required)

Sets the DSCP priority for an IP path

according to services carried by the IP

path.

This parameter is available when

IPPATH. PathTypeis set to FIXED(Fixed

QoS).

eRAN





134



The following table describes the parameters that must be set in an eNodeBPath MO to

enable dynamic flow control in link mode. If the S1 interface is set up in endpoint mode, the

eNodeBPath MO does not need to be configured.

ParameterName

ParameterID


IP Path ID eNodeBPath

. IpPathId

Network plan

(negotiation

not required)

Set this parameter to the ID of the IP

path where the data requiring dynamic

flow control is carried.

Application

Type

eNodeBPath

. AppType

Network plan

(negotiation

not required)

Set this parameter to S1(S1) because

dynamic flow control is generally

enabled on the S1 interface.

S1 Interface

ID

eNodeBPath

. S1Interface

Id

Network plan

(negotiation

not required)


plan.

9.7.4 Precautions

For details about IP PM, see IP Performance Monitor Feature Parameter Description.


N/A

9.7.6 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs



into the Configuration Management Express (CME) for batch configuration. For detailed

instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for

the eNodeB.





file.



parameters.

All the MOs listed in the following table except the IPPATH and DIFPRI MOs require a

user-defined template. It is recommended that user-defined templates be derived from the

En_Basic_eRAN_Sharing_Link template. It is also recommended that the parameters in theMOs (except for the IPPATH MO) be added to the Base Station Transport Data sheet.

eRAN





135



Table 9-5 Parameters related to transport congestion control

MO Sheet in theSummaryData File


RSCGRP Base Station

Transport Data

or user-defined

sheet


Slot No., Transport Resource

Group Bear Type, Subboard

Type, Bearing Port Type,

Bearing Port No., Transport

Resource Group ID, Rate

Unit, Tx Bandwidth, Rx

Bandwidth, TX Committed

Burst Size(Kbit), TX

Excessive Burst Size(Kbit),

Operator ID, Scheduling

Weight, TX CommittedInformation Rate, RX

Committed Information

Rate, TX Peak Information

Rate, RX Peak Information

Rate, TX Peak Burst

Size(Kbit)

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.

IPPATH DevIPPattern Cabinet No., Subrack No.,

Slot No., Subboard Type,

Port No., IP Path ID, Join

Transport Resource Group,

Transport Resource GroupID, Path Type, DSCP, Local

IP, Peer IP, Transport

Resource Type, Path check,

IPMUX Switch Flag, Max

Subframe length, Max frame

length, Max Timer,

Description Info

-

DIFPRI Common Data Priority Rule, Signaling

Priority, OM High Priority,

OM Low Priority, IP Clock

Priority

The summary data

file needs to be

customized based on

the template namedEn_Basic_eRAN_Sh

aring_Link.

eRAN





136





RSCGRPALG Base Station

Transport Data

or user-defined

sheet


Slot No., Subboard Type,

Bearing Port Type, Bearing

Port No., Transport Resource

Group ID, TX Traffic

Shaping Switch, TX

Bandwidth Adjustment

Switch, RX Bandwidth

Adjustment Switch, Packet

Loss Ratio Down

Threshold(per mill), Delay

Down Threshold(ms),

Traffic Control Switch, OM,FTP Traffic Control Switch,

PQ Number, Congestion

Time Threshold(ms),

Congestion Clear Time

Threshold(ms), TX Reserved

Bandwidth(Kbit/s), RX

Reserved Bandwidth(Kbit/s),

Drop Packet Number

Threshold(packet)

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.

LR Base Station

Transport Dataor user-defined

sheet


Slot No, Subboard Type,Port Type, Port No., LR

Switch, UL Committed

Information Rate,

Committed Burst Size,

Excess Burst Size, DL

Committed Information Rate

The summary data

file needs to becustomized based on

the template named

En_Basic_eRAN_Sh

aring_Link.


Transport Data

or user-defined

sheet

User Data Type Transfer

Parameter Group ID.,

Priority Rule, Priority, Act

Factor, Primary Transport

Resource Type, Primary PortLoad Threshold, Primary To

Secondary Port Load Ratio

Threshold

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sharing_Link.

GTRANSPARA Base Station

Transport Data

or user-defined

sheet

Resource Group Scheduling

Weight Switch, Rate Config

Type

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.

eRAN





137





ENODEBPATH Base Station

Transport Data

or user-defined

sheet

IP Path ID, Application

Type, S1 Interface ID, X2

Interface ID

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.

PRI2QUE Base Station

Transport Data

or user-defined

sheet

PriOfQue0, PriOfQue1,



PriOfQue6

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.

IPPMSESSION Base Station

Transport Data

or user-defined

sheet

IP PM Session ID, IP PM

Type, Bind IP Path, IP Path

ID, Local IP, Peer IP, DSCP,

Activate Direction

The summary data

file needs to be

customized based on

the template named

En_Basic_eRAN_Sh

aring_Link.





Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the

CME to Perform Batch Configuration for Newly Deployed eNodeBs". For online help, press





Configuration Data (U2000 client mode), or choose LTE Application > Export Data >

Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeBdata stored on the CME into the customized summary data file.









eRAN





138





----End




Step 1 In the planned data area, click Base Station in the upper left corner of the configuration

window.




Step 4 In area 3, double-click the MO in the Object Name column. All the parameters in this MOare displayed in area 4.





----End

Using MML Commands

Transport congestion control involves transport differentiated flow control and transportdynamic flow control.

eRAN





139



l Transport Differentiated Flow Control

The configuration procedure is as follows:

Step 1 Run the SET RSCGRPALG command to configure the switches for the traffic shaping and

back-pressure algorithms.



Step 3 Run the MOD UDTPARAGRP command to set the service priority.

Step 4 Run the SET PRI2QUE command to configure the mapping between service priorities and

queues.

Step 5 Run the SET RSCGRPALG command to configure the number of PQ queues.

----End

l Transport Dynamic Flow Control

The configuration procedure is as follows:

Step 1 Run the SET RSCGRPALG command to enable the bandwidth adjustment function for a


Step 2 Perform the following operations in different modes:

l In link mode, run the ADD IPPMSESSION command to configure IP PM and bind the

IP PM session to an IP path. If they are not bound, dynamic bandwidth adjustment

cannot be performed on transport resource groups.

l In endpoint mode, run the ADD IPPMSESSION command to disable the binding of the

IP PM session to an IP path.

----End


l Transport Differentiated Flow Control

SET RSCGRPALG:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0, TXSSW=ON,

TCSW=ENABLE;LST UDT;

MOD UDTPARAGRP: UDTPARAGRPID=48, PRIRULE=DSCP, PRI=0;

SET PRI2QUE: PRI0=48, PRI1=40;SET RSCGRPALG: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, PQN=3;

l Transport Dynamic Flow Control

SET RSCGRPALG: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, TXBWASW=ON,RXBWASW=ON;

(In link mode)ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=FOUR_TUPLE, BINDPATH=YES,

PATHID=0;(In link mode)ADD ENODEBPATH:IPPATHID=0,APPTYPE=S1,S1INTERFACEID=0;

(In endpoint mode)ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=FOUR_TUPLE, BINDPATH=NO,

LOCALIP="5.5.33.5", PEERIP="138.32.1.50", IPPMDSCP=0;


Note that:


l

The methods used to access a cell and set up a dedicated bearer depend on the type of UE. For detailed operations, see the user guide provided by the UE manufacturer.

eRAN





140




injection tools and data types. User Datagram Protocol (UDP) packet injection is used as

an example in this section.

NOTE

Anonymization has been performed on S1 interface tracing tasks, and therefore no security risk exists.


Prerequisites

The committed bandwidth of a physical port is greater than the sum of the bandwidths of all

transport resource groups on this port so that the bandwidths configured for each group are the

same as the actual admission bandwidths.

Procedure


Step 1 Run the LST RSCGRP command to check bandwidth settings of a transport resource group.

Step 2 Run the LST RSCGRPALG command to check the settings of the traffic shaping and back-

pressure switches. Then, record the values.

Transport differentiated flow control requires that TX Traffic Shaping Switch be On and

Traffic Control Switch be Enable.

Step 3 Run the LST STANDARDQCI command to check the uplink scheduling priority factors for

QCIs 6 and 8, and record the query results.

Step 4 Run the MOD STANDARDQCI command to change the uplink scheduling priority factors

for QCIs 6 and 8 to 1000 and 500, respectively.

Step 5 Use UE 1 to set up a non-GBR bearer with a QCI of 6, and use UE 2 to set up a non-GBR

bearer with a QCI of 8. Then, trace S1 signaling to see whether the dedicated bearers have

been successfully set up.

Step 6 Use UEs 1 and 2 to perform uplink UDP packet injection with injection rates higher than the

bandwidth capacities of the corresponding transport resource groups.

Step 7 Run the DSP RSCGRP command to check whether the value of Non-Realtime TX

Bandwidth is consistent with the TX bandwidth configured for the transport resource group.

Transport differentiated flow control is performed on the uplink. Therefore, the expected

result is that the bandwidth after traffic shaping and back-pressure is less than or equal to the bandwidth capacity configured for the transport resource group.

Step 8 On the service server in the EPC, check whether the traffic proportion between UEs 1 and 2 is

consistent with the proportion of uplink scheduling priority factors between UEs 1 and 2

(configured in Step 4). If the two proportions are consistent, transport differentiated flow

control takes effect.

Step 9 Run the SET RSCGRPALG command to turn off the TX traffic shaping and back-pressure

switches.

Step 10 Use UEs 1 and 2 to continue uplink UDP packet injection.

Step 11 Run the DSP RSCGRP command to check whether the value of Non-Realtime TXBandwidth is consistent with the TX bandwidth configured for the transport resource group.

eRAN





141



After the traffic shaping and back-pressure switches are turned off, the injection rates are not

limited within the bandwidth configured for the transport resource group. Therefore, the

traffic proportion between UEs 1 and 2 (which can be obtained on the service server in the

EPC) is inconsistent with the proportion of uplink scheduling priority factors between UEs 1

and 2 (configured in Step 4).

Step 12 Run the SET RSCGRPALG and MOD STANDARDQCI commands to restore the

configurations.

----End


Prerequisites

Transport differentiated flow control is functional. For detailed configuration and verification,

see 9.7.7 Activation Observation.

Procedure


Step 1 Run the LST RSCGRPALG command to check switch settings and the values of Packet

Loss Ratio Down Threshold(per mill) and Delay Down Threshold(ms). Then, record the

thresholds.

If TX Bandwidth Adjustment Switch and RX Bandwidth Adjustment Switch are On, transport

dynamic flow control is activated.

Step 2 Run the LST IPPMSESSION command to check IP PM session settings and the value of

Activate Direction. Then, record the parameter values.

The admission bandwidths of a transport resource group can be dynamically adjusted based

on transmission link quality only if an IP PM session is bound to an IP path in the group.

Step 3 Run the DSP IPPMSESSION command to check IP PM session status.

If Activate State(Up) or Activate State(Down), depending on the activation direction, is IP

PM UP, the IP PM session works normally.

Step 4 Enable a UE to access a cell. Use the UE to perform uplink UDP packet injection with an

injection rate higher than the TX bandwidth configured for the transport resource group.

Step 5 Run the DSP RSCGRP command to check the uplink and downlink admission bandwidths of

the transport resource group, and record the query results. Check whether the value of Non-

Realtime TX Bandwidth is consistent with the uplink admission bandwidth of the transport

resource group.

If transport differentiated flow control is functional, the queried two bandwidths should be

consistent.

Step 6 Use a tool, such as a network impairment emulator, to simulate packet loss on the IP path with

the packet loss rate higher than the value of Packet Loss Ratio Down Threshold(per mill).

Run the DSP IPPMSESSION command to check whether the value of TX Loss Rate(per

mill) is the same as the packet loss rate.

If the value of TX Loss Rate(per mill) is the same as the packet loss rate, IP PM measureskey performance indicators (KPIs) of the transport network normally.

eRAN





142



Step 7 Run the DSP RSCGRP command to check the uplink admission bandwidth of the transport

resource group. Compare these bandwidths with the values recorded in Step 5.

If the values obtained in this step are less than the values recorded in Step 5, transport

dynamic flow control takes effect. The value of Non-Realtime TX Bandwidth should be less

than the TX bandwidth configured for the transport resource group and equal to the uplink admission bandwidth adjusted during transport dynamic flow control.

Step 8 Stop simulating packet loss, and continue UDP packet injection.

Step 9 Run the DSP RSCGRP command.

If the value of Non-Realtime TX Bandwidth is restored to the TX bandwidth configured for

the transport resource group, and the uplink and downlink admission bandwidths of the

transport resource group are restored to the configured values, transport dynamic flow control

takes effect.

----End


N/A

9.7.9 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on

eNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure for feature deactivation is similar to that for


Existing eNodeBs." In the procedure, modify parameters according to Table 9-6.

Table 9-6 Parameters related to transport congestion control



RSCGRPALG RSCGRPALG or

user-defined sheet

TCSW, TXSSW l Set TCSW to

DISABLE(Disa

ble).

l Set TXSSW to

OFF(Off).

RSCGRPALG UDTPARAGRP or

user-defined sheet

TXBWASW,

RXBWASW

l Set TXBWASW

to OFF(Off).

l Set RXBWASW

to OFF(Off).

eRAN





143




On the CME, set parameters according to Table 9-6. For detailed instructions, see "Using the

CME to Perform Single Configuration."

Using MML Commands

l To deactivate transport differentiated flow control

Run the SET RSCGRPALG command to turn off Traffic Control Switch and TX

Traffic Shaping Switch.

l To deactivate transport dynamic flow control

Run the SET RSCGRPALG command to turn off TX Bandwidth Adjustment Switch

and RX Bandwidth Adjustment Switch.


l Deactivating transport differentiated flow controlSET RSCGRPALG: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, TCSW=DISABLE, TXSSW=OFF;

l Deactivating transport dynamic flow control

SET RSCGRPALG: SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, TXBWASW=OFF,RXBWASW=OFF;

9.8 Performance Monitoring

This section describes how to use the U2000 client to monitor the running status of the

transport resources of IP paths, transport resource groups, and physical ports in real time.

IP Path Monitoring

To create an IP path monitoring task on an U2000 client, perform the following steps:

Step 1 Choose Monitor > Signaling Trace > Signaling Trace Management. On the displayed

Signaling Trace Management tab page, choose Trace Type > Base Station Device and

Transport > Transport Performance Monitoring > Transport Link Traffic Monitoring

from the navigation tree on the left. Double-click Transport Link Traffic Monitoring.

Step 2 In the displayed Transport Link Traffic Monitoring dialog box, select an eNodeB to be

monitored and click Next.

Step 3 In the displayed dialog box, select an IP path to be monitored and select the Include IPPM

Statistic check box if the IP path is bound to an IP PM session, as shown in Figure 9-9.

eRAN





144



Figure 9-9 Transport Link Traffic Monitoring dialog box

Step 4 View the information about the IP path, such as the TX rate and RX rate.

Figure 9-10 Checking IP path status

----End

Transport Port Monitoring

To create a transport port monitoring task on an U2000 client, perform the following steps:

Step 1 Choose Monitor > Signaling Trace > Signaling Trace Management. On the displayed

Signaling Trace Management tab page, choose Trace Type > Base Station Device and

Transport > Transport Performance Monitoring > Transport Port Traffic Monitoringfrom the navigation tree on the left. Double-click Transport Port Traffic Monitoring.

eRAN





145



Step 2 In the displayed Transport Port Traffic Monitoring dialog box, select an eNodeB to be

monitored and click Next.

Step 3 In the displayed dialog box, set Port Type and Monitor Type, as shown in Figure 9-11.

Figure 9-11 Transport Port Traffic Monitoring dialog box

Step 4 Select different objects to be monitored and view the monitoring results as follows:

l To monitor a physical port, set Port Type to Physical Port and Protocol Type to IP, and

then view the monitoring results shown in Figure 9-12.

– If Physical Port Type is set to TUNNEL, the TX and RX rates at the network layer

are calculated for IP ports.

– If Physical Port Type is set to other values, the TX and RX rates at the data link

layer are calculated for IP ports.

Figure 9-12 Monitor result of a physical port

eRAN





146



l To monitor a transport resource group, set Port Type to RSCGRP and view the real-

time load, GBR load, and traffic of the transport resource group.

----End

9.9 Parameter Optimization

None

9.10 Troubleshooting


Fault Description

A UE fails to access a network, and the S1AP_INITIAL_CONTEXT_SETUP_FAIL message

traced over the S1 interface indicates the cause value "transport---transport -resource-

unavailable."

Fault Handling

To rectify this fault, perform the following steps:

Step 1 Check IP path status.

If the transport network can be checked using GTPU echo ping commands, perform the

following steps:

1. Run the MOD GTPU command to enable the static GPRS Tunneling Protocol-User

Plane (GTP-U) check.

2. Run the DSP IPPATH command to check IP path status.

If... Then...

The status is faulty Check the configurations of the IP path,

route, and transport network. If any

parameter is incorrectly set, change thesetting.

The status is normal Go to Step 2.

If you cannot use the GTPU echo ping commands to check the transport network, perform the

following steps:

1. Run the MOD GTPU command to enable the static GPRS Tunneling Protocol-User

Plane (GTP-U) check.

2. On the U2000 client, start GTP-U tracing and check echo request and echo responsemessages.

eRAN





147



If... Then...

If there is no echo response to an echo

request

The IP path is faulty.

Check the configurations of the IP path,

route, and transport network. If any parameter is incorrectly set, change the

setting.

If there is an echo response to an echo

request

The IP path is functional.

Go to Step 2.

Step 2 Run the LST IPPATH command to query the transport resource group to which the IP path

belongs and check that the IP address of the peer S-GW is correct.

NOTE

l The IP path status may be normal even if the IP address of the peer S-GW is incorrect.

l If the query result indicates that the IP path does not belong to any transport resource group, the IP

path is managed by the default transport resource group.

Step 3 Run the LST STANDARDQCI command to check the uplink or downlink Min_GBR

mapped to the QCI of the default bearer. If the uplink or downlink Min_GBR mapped to a

QCI in the range of 6 to 9 is set to 0, the corresponding bearer cannot be admitted. To avoid

this problem, modify the Min_GBR.

The QCI of the default bearer is indicated in the S1_INITIAL_CONTEXT_SETUP_REQ

message, which can be traced over the S1 interface.

Step 4 Run the DSP RSCGRP command to check that the admission bandwidths of the transportresource group are sufficient.

NOTE

If the bandwidths are low, admission may fail.

Step 5 Run the LST TACALG command to check that the admission thresholds for gold, silver,

bronze, and non-GBR services are not too low.

Ensure that the thresholds are set based on the network plan or retain their default values.

Step 6 If the fault persists, contact Huawei for technical support.

----End


Fault Description

Transport differentiated flow control is performed on UEs that use services with different

QCIs. The traffic proportion between these services is not consistent with the configured

proportion.

Fault Handling

To rectify this fault, perform the following steps:

eRAN





148



Step 1 Check the signaling messages S1_ERAB_SETUP_REQ and S1_ERAB_SETUP_RSP to see

whether the dedicated bearers for UEs are successfully set up.

l If all required dedicated bearers fail to be set up for a UE, then flow control is performed

on the default bearer of this UE, and the effect of flow control may not be as expected.

l If all dedicated bearers are successfully set up, go to Step 2.

Step 2 Run the LST STANDARDQCI command to see whether the uplink scheduling priority

factors for different QCIs are consistent with the planned values. If the priority factors are

inconsistent with the planned values, run the MOD STANDARDQCI command to change

the priority factors.

----End

If the fault persists, contact Huawei for technical support.

9.10.3 Alarms

If an alarm listed in Table 9-7 is reported, clear the alarm by referring to Alarm Reference.

Table 9-7 TRM-related alarms

Alarm ID Alarm Name NE Feature ID Feature Name

ALM-25900 IP PM

Activation

Failure

eNodeB LOFD-0030120

1

IP Performance

Monitoring

ALM-25886 IP Path Fault eNodeB None None

ALM-25952 User Plane

Bearer Link

Fault

eNodeB None None

eRAN





149



10 Parameters

Table 10-1 Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

TXBWA

MIN

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301202

/

TDLOF

D-00301

202

Transpo

rt

Dynami

c Flow

Control

Meaning: Indicates the minimum amount of adjusted

TX bandwidth. If TXBWASW is set to ON, the

adjusted bandwidth should be at least greater than this

minimum.The UMTS currently does not support this

function.

GUI Value Range: 64~10000000

Unit: kbit/s

Actual Value Range: 64~10000000

Default Value: 1024

RSCGR

PALG

RXBW

AMIN

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301202

/

TDLOF

D-00301

202

Transpo

rt

Dynami

c Flow

Control

Meaning: Indicates the minimum amount of adjusted

RX bandwidth. If RXBWASW is set to ON, the

adjusted bandwidth must be at least greater than this

minimum.The UMTS currently does not support this

function.


Unit: kbit/s


Default Value: 1024

eRAN


Description 10 Parameters



150



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

PT ADD

RSCGR

P

DSP

RSCGR

P

MOD

RSCGR

P

RMV

RSCGR

PLST

RSCGR

P

None None Meaning: Indicates the type of port where a

transmission resource group is carried. The LTE

currently does not support STM1, IMA, UNI, or

FRAATM.

GUI Value Range: IMA(IMA Group), UNI(UNI

Link), STM1(STM1), FRAATM(FRAATM Link),

PPP(PPP Link), MPGRP(Multi-link PPP Group),

ETH(Ethernet Port), ETHTRK(Ethernet Trunk),

TUNNEL(Tunnel)

Unit: None

Actual Value Range: IMA, UNI, STM1, FRAATM,

PPP, MPGRP, ETH, ETHTRK, TUNNELDefault Value: None

RSCGR

P

TXBW ADD

RSCGR

P

MOD

RSCGR

P

DSP

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

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 minimum rate supported by the

UMPTb or UMDU is 64 kbit/s. 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,

UMDU or UTRPc can be configured with a maximum

of 1 Gbit/s TX bandwidth. The UCCU can be

configured with a maximum of 10 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.


Unit: None


Default Value: None

eRAN





151



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

RXBW ADD

RSCGR

P

MOD

RSCGR

P

DSP

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

WRFD-

0106101

0

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-118605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

HSDPA

Flow

Control

Enhanced

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the RX bandwidth of a

transmission resource group. To LTE, this parameter

value is also used as the downlink transport admission

bandwidth. The minimum rate supported by the

UMPTb or UMDU is 64 kbit/s. The LMPT can be

configured with a maximum of 540 Mbit/s RX

bandwidth. The WMPT can be configured with a

maximum of 300 Mbit/s RX bandwidth. The UMPT,


of 1 Gbit/s RX bandwidth. The UCCU can be

configured with a maximum of 10 Gbit/s RX

bandwidth. The value of RX bandwidth is set to the

maximum value of RX bandwidth supported by the board when it bigger than the maximum one.


Unit: None


Default Value: None

RSCGR

P

TXCIR ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

eSharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the transmit CIR of the

transmission resource group. The LMPT can be

configured with a maximum of 360 Mbit/s TX

committed information rate. The UMPT, UMDU or UTRPc can be configured with a maximum of 1

Gbit/s TX committed information rate. The UCCU

can be configured with a maximum of 10 Gbit/s TX

committed information rate. The value of TX

committed information rate is set to the maximum

value of TX committed information rate supported by

the board when it bigger than the maximum one.


Unit: None


Default Value: None

eRAN





152



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

RXCIR ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the receive CIR of the

transmission resource group. This parameter value is

used as the downlink transport admission bandwidth

for non-flow-control services. The LMPT can be

configured with a maximum of 540 Mbit/s RX

committed information rate. The UMPT, UMDU or

UTRPc can be configured with a maximum of 1

Gbit/s RX committed information rate. The UCCU

can be configured with a maximum of 10 Gbit/s RX

committed information rate. The value of RX

committed information rate is set to the maximum

value of RX committed information rate supported by

the board when it bigger than the maximum one. Onlythe LTE supports this function currently.


Unit: None


Default Value: None

RSCGR

P

TXPIR ADD

RSCGR

P

MOD

RSCGR P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharingon

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the transmit PIR of the


configured with a maximum of 360 Mbit/s TX peak

information rate. The UMPT, UMDU or UTRPc can

be configured with a maximum of 1 Gbit/s TX peak information rate. The UCCU can be configured with a

maximum of 10 Gbit/s TX peak information rate. The

value of TX peak information rate is set to the

maximum value of TX peak information rate

supported by the board when it bigger than the

maximum one.


Unit: None


Default Value: None

eRAN





153



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

RXPIR ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the receive PIR of the

transmission resource group. This parameter value is

used as the downlink transport admission bandwidth.

The LMPT can be configured with a maximum of 540

Mbit/s RX peak information rate. The UMPT, UMDU

or URTPc can be configured with a maximum of 1

Gbit/s RX peak information rate. The UCCU can be

configured with a maximum of 10 Gbit/s RX peak

information rate. The value of RX peak information

rate is set to the maximum value of RX peak

information rate supported by the board when it

bigger than the maximum one. Only the LTE supports

this function currently.GUI Value Range: 64~10000000

Unit: None


Default Value: None

eRAN





154



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

GTRAN

SPARA

LPSCH

SW

SET

GTRAN

SPARA

LST

GTRAN

SPARA

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king

Meaning: Indicates the switch used to control whether

to allocate bandwidths to transmission resource

groups on the physical port based on their scheduling

weights. When RATECFGTYPE (the rate

configuration type) is set to SINGLE_RATE and

Physical Port Up Link OverBooking Switch or

Physical Port Down Link OverBooking Switch is set

to OFF, different values of this parameter lead to

different bandwidth allocation methods as follows: (1)

If this parameter is set to DISABLE and the sum of

TX bandwidths of the associated resource groups

exceeds the bandwidth of the physical port, each

resource group is allocated a bandwidth that is directly proportional to its configured TX bandwidth; (2) If

this parameter is set to ENABLE and the sum of TX

bandwidths of the associated resource groups exceeds

the bandwidth of the physical port, each resource

group is allocated a bandwidth that is directly

proportional to its scheduling weight. When

RATECFGTYPE (the rate configuration type) is set to

DUAL_RATE, different values of this parameter lead

to different CIR allocation methods as follows: (1) If

the sum of CIRs of the associated resource groups

exceeds the bandwidth of the physical port, each

resource group is allocated a CIR that is directly proportional to its configured CIR; (2) If the sum of

CIRs of the associated resource groups is smaller than

the bandwidth of the physical port, each resource

group is allocated a non-CIR that is directly

proportional to its scheduling weight. In this case, the

PIR of a resource group is the sum of the CIR and the

non-CIR.

GUI Value Range: DISABLE(Disable),

ENABLE(Enable)

Unit: None

Actual Value Range: DISABLE, ENABLE

Default Value: DISABLE(Disable)

eRAN





155



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

WEIGH

T

ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the scheduling weight of a

transmission resource group. This parameter is used in

calculating the bandwidth scheduled to a resource

group, which helps achieve the user admission

control.


Unit: None


Default Value: 100

GTRAN

SPARA

RATEC

FGTYP

E

SET

GTRAN

SPARA

LST

GTRAN

SPARA

LOFD-0

03011 /

TDLOF

D-00301

1

Enhance

d

Transmi

ssion

QoS

Manage

ment

Meaning: Indicates the rate configuration mode of

transmission resource groups in the BS, which can be

set to SINGLE_RATE or DUAL_RATE. The dual rate

configuration refers to the hybrid of the peak

information rate (PIR) and committed information rate

(CIR). If this parameter is set to SINGLE_RATE, the

transmission resource group performs traffic shaping based on its transmit bandwidth. If this parameter is

set to DUAL_RATE, the transmission resource group

performs traffic shaping based on PIR and the

transmission admission algorithm ensures that the

non-flow-controllable traffic does not exceed CIR.

GUI Value Range: SINGLE_RATE(Single Rate),

DUAL_RATE(Dual Rate)

Unit: None

Actual Value Range: SINGLE_RATE, DUAL_RATE

Default Value: SINGLE_RATE(Single Rate)

eRAN





156



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LR CIR SET LR

LST LR

WRFD-

0106101

0

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/TDLOF

D-00301

102

GBFD-1

18605

HSDPA

Flow

Control

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

IP QOS

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 or UMDU 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.For the GTMU, the

value of CIR ranges from 64 to 100000. If this

parameter is set to a value greater than the maximum

allowed value or less than the minimum allowed

value, the maximum or the minimum allowed value

takes effect.GUI Value Range: 32~10000000

Unit: kbit/s


Default Value: None

LR DLCIR SET LR

LST LR

WRFD-

050402

LOFD-0

0301101

/TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

IubInterface

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

IP QOS

Meaning: Indicates the DL committed information

rate after rate limitation is configured at a port.The

parameter does not take effect in GSM.For UMTS,if

the downlink flow control switch is set to

DYNAMIC_BW_SHAPING or

STATIC_BW_SHAPING, this parameter is valid. If the downlink flow control switch is set to

BW_SHAPING_ONOFF_TOGGLE, this parameter is

valid when traffic congestion is detected. In other

cases, this parameter is invalid.For LTE, this

parameter computes the value of Physical Port Down

Link Admission.The minimum rate supported by the

UMPTb or UMDU is 64 kbit/s.


Unit: kbit/s


Default Value: None

eRAN





157



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IPPATH LOCAL

IP

ADD

IPPATH

MOD

IPPATH

LST

IPPATH

WRFD-

050402

GBFD-1

18601

GBFD-1

18611

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abis

over IP

Abis IP

over

E1/T1

Meaning: Indicates the local IP address of an IP path.

The value 0.0.0.0 indicates that the local IP address

needs to be negotiated.

GUI Value Range: Valid IP address

Unit: None

Actual Value Range: Valid IP address

Default Value: None

IPPATH PEERIP ADD

IPPATH

MOD

IPPATH

LST

IPPATH

WRFD-

050402

GBFD-1

18601

GBFD-1

18611

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abis

over IP

Abis IP

over

E1/T1

Meaning: Indicates the peer IP address of the IP path.


Unit: None


Default Value: None

IPPATH PATHT

YPE

ADD

IPPATH

MOD

IPPATH

LST

IPPATH

GBFD-1

18601

GBFD-1

18611

Abis

over IP

Abis IP

over

E1/T1

Meaning: Indicates the type of the IP path. FIXED

indicates that this IP path is used to carry the service

with specified Quality of Service (QoS), that is, with a

specified DSCP. ANY indicates that this IP Path can

be used to carry services of any QoS and hence is used

to carry the service without a specified DSCP.

GUI Value Range: FIXED(Fixed QoS), ANY(Any

QoS)

Unit: None

Actual Value Range: FIXED, ANY

Default Value: FIXED(Fixed QoS)

eRAN





158



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IPPATH DSCP ADD

IPPATH

MOD

IPPATH

LST

IPPATH

WRFD-

050402

GBFD-1

18601

GBFD-1

18611

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abis

over IP

Abis IP

over

E1/T1

Meaning: Indicates the differentiated services code

point (DSCP) of the services carried on an IP path.


Unit: None


Default Value: None

IPPATH RSCGR

PID

ADD

IPPATH

MOD

IPPATH

LST

IPPATH

WRFD-

0213040

6

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

IP QOS

Meaning: Indicates the ID of the transmission

resource group established on an IP path.


Unit: None


Default Value: 0

IPPATH JNRSCGRP

ADDIPPATH

MOD

IPPATH

LST

IPPATH

WRFD-0213040

6

GBFD-1

18605

Transmission

Recours

e

Sharing

on

Iub/Iur

Interface

IP QOS

Meaning: Indicates whether the IP path joins atransmission resource group. If this parameter is set to

DISABLE, the IP path is established on the default

transmission resource group on a specific physical

port.


ENABLE(Enable)

Unit: None



eRAN





159



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Standard

Qci

UlMinG

br

MOD

STAND

ARDQC

I

LST

STAND

ARDQC

I

LOFD-0

0101502

/

TDLOF

D-00101

502

LOFD-0

0301101

LOFD-0

0301102

LOFD-0

0301103TDLBF

D-00202

5

TDLOF

D-00101

5

Dynami

c

Scheduli

ng

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Transpo

rt

Resourc

e

Overloa

d

Control

Basic

Scheduli

ng

Enhance

d

Scheduli

ng

Meaning: Indicates the uplink minimum guaranteed

bit rate of the non-GBR service.

GUI Value Range: MinGbrRate_0_KB(0kB/s),

MinGbrRate_1_KB(1kB/s),









MinGbrRate_512_KB(512kB/s)

Unit: kB/s

Actual Value Range: MinGbrRate_0_KB,

MinGbrRate_1_KB, MinGbrRate_2_KB,




MinGbrRate_256_KB, MinGbrRate_512_KB

Default Value: MinGbrRate_1_KB(1kB/s)

eRAN





160



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Extende

dQci

UlMinG

br

ADD

EXTEN

DEDQC

I

MOD

EXTEN

DEDQC

I

LST

EXTEN

DEDQC

I

LOFD-0

0101502

/

TDLOF

D-00101

502

LOFD-0

0301101

LOFD-0

0301102

/

TDLOF

D-00301

102

LOFD-0

0301103

Dynami

c

Scheduli

ng

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Transpo

rt

Resourc

e

Overloa

d

Control

Meaning: Indicates the uplink minimum guaranteed

bit rate of the non-GBR service.












Unit: kB/s








Standard

Qci

DlMinG

br

MOD

STANDARDQC

I

LST

STAND

ARDQC

I

LOFD-0

0101502/

TDLOF

D-00101

502

LOFD-0

0301101

LOFD-0

0301103

LOFD-0

03016 /

TDLOFD-00301

6

Dynami

cScheduli

ng

Transpo

rt

Overboo

king

Transpo

rt

Resourc

e

Overload

Control

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the downlink minimum

guaranteed bit rate of the non-GBR service.GUI Value Range: MinGbrRate_0_KB(0kB/s),











Unit: kB/s








eRAN





161



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Extende

dQci

DlMinG

br

ADD

EXTEN

DEDQC

I

MOD

EXTEN

DEDQC

I

LST

EXTEN

DEDQC

I

LOFD-0

0101502

/

TDLOF

D-00101

502

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301103

/

TDLOF

D-00301

103

LOFD-0

03016 /

TDLOF

D-00301

6

Dynami

c

Scheduli

ng

Transpo

rt

Overboo

king

Transpo

rt

Resourc

e

Overloa

d

Control

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the downlink minimum

guaranteed bit rate of the non-GBR service.












Unit: kB/s








eRAN





162



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Extende

dQci

FlowCtr

lType

ADD

EXTEN

DEDQC

I

MOD

EXTEN

DEDQC

I

LST

EXTEN

DEDQC

I

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

LOFD-0

0301103

/

TDLOF

D-00301

103

LOFD-0

03016 /

TDLOF

D-00301

6

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Transpo

rt

Resourc

e

Overloa

d

Control

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates whether to enable flow control for

the QCI.

GUI Value Range: FLOW_CTRL(Flow Control),

NON_FLOW_CTRL(Non Flow Control)

Unit: None

Actual Value Range: FLOW_CTRL,

NON_FLOW_CTRL

Default Value: FLOW_CTRL(Flow Control)

DIFPRI PRIRUL

E

SET

DIFPRI

LST

DIFPRI

WRFD-

050402

LBFD-0

0300201

/

TDLBF

D-00300

201

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

DiffServ

QoS

Support

IP QOS

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.

GUI Value Range: IPPRECEDENCE(IP Precedence),

DSCP(DSCP)

Unit: None

Actual Value Range: IPPRECEDENCE, DSCP

Default Value: DSCP(DSCP)

eRAN





163



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

DIFPRI SIGPRI SET

DIFPRI

LST

DIFPRI

WRFD-

050402

LBFD-0

0300201

/

TDLBF

D-00300

201

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

DiffServ

QoS

Support

IP QOS

Meaning: Indicates the priority of signaling. The

priority has a positive correlation with the value of

this parameter.


Unit: None


Default Value: 48

DIFPRI OMHIG

HPRI

SET

DIFPRI

LST

DIFPRI

WRFD-

050402

LBFD-0

0300201

/

TDLBF

D-00300

201

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

DiffServ

QoS

Support

IP QOS

Meaning: Indicates the priority of the high-level OM

data. The priority has a positive correlation with the

value of this parameter.


Unit: None


Default Value: 46

DIFPRI OMLO

WPRI

SET

DIFPRI

LST

DIFPRI

WRFD-

050402

LBFD-0

0300201

/

TDLBF

D-00300

201

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

DiffServ

QoS

Support

IP QOS

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


Unit: None


Default Value: 18

eRAN





164



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

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.


Unit: None


Default Value: 46

UDT UDTPA

RAGRP

ID

ADD

UDT

MOD

UDT

LST

UDT

None None Meaning: Indicates the ID of the transport parameter

group related to the services corresponding to an

QCI.User data type numbers 1~9 correspond to user

data type transfer parameter group IDs 40~48, which

are automatically configured by the BS.


Unit: None


Default Value: None

UDTPARAGRP

UDTPARAGRP

ID

ADDUDTPA

RAGRP

LST

UDTPA

RAGRP

MOD

UDTPA

RAGRP

RMV

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.


Unit: None


Default Value: None

UDT UDTNO ADD

UDT

MOD

UDT

RMV

UDT

LST

UDT

None None Meaning: Indicates the number of the user data

type.Numbers 1~9 are standard user data types, which

are automatically configured by the BS. Numbers

10~254 are extended user data types.


Unit: None


Default Value: None

eRAN





165



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UDTPA

RAGRP

PRIRUL

E

ADD

UDTPA

RAGRP

MOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

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

GUI Value Range: IPPRECEDENCE(IP Precedence),

DSCP(DSCP)

Unit: None

Actual Value Range: IPPRECEDENCE, DSCP

Default Value: DSCP(DSCP)

UDTPARAGRP PRI ADDUDTPA

RAGRP

MOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

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.


Unit: None


Default Value: None

UDTPA

RAGRP

ACTFA

CTOR

ADD

UDTPA

RAGRP

MOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

None None Meaning: Indicates the activity factor of the services

corresponding to an QCI.


Unit: %


Default Value: 0

RSCGR

PALG

TXRSV

BW

SET

RSCGR

PALG

LSTRSCGR

PALG

LOFD-0

0301101

/

TDLOFD-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Overboo

kingTranspo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the TX bandwidth reserved for

signaling data, OM data, or real-time services. This

parameter should be set to a value less than the TX

bandwidth of a transmission resource group. It isrecommended that the reserved TX bandwidth be set

to a value less than or equal to 3% of the TX

bandwidth of a transmission resource group. This

parameter does not take effect in UTMS.


Unit: kbit/s


Default Value: 0

eRAN





166



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

RXRSV

BW

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the reserved RX bandwidth, which

should be set to a value smaller than or equal to the

RX bandwidth of a transmission resource group. The

UMTS currently does not support this function.


Unit: kbit/s


Default Value: 0

TACAL

G

RSCGR

PULCA

CSWIT

CH

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king

Meaning: Indicates the switch that is used to control

whether to apply UL admission control to a resource

group.

GUI Value Range: OFF(Off), ON(On)

Unit: None

Actual Value Range: OFF, ON

Default Value: ON(On)

TACAL

G

RSCGR

PDLCA

CSWITCH

SET

TACAL

GLST

TACAL

G

LOFD-0

0301101

/TDLOF

D-00301

101

Transpo

rt

Overbooking


whether to apply DL admission control to a resource

group.GUI Value Range: OFF(Off), ON(On)

Unit: None



TACAL

G

PORTU

LCACS

W

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to apply UL admission control to a physical

port. If this parameter is set to ON, UL admission

control is applied to the physical port. If this

parameter is set to OFF, UL admission control is not

applied to the physical port.


Unit: None


Default Value: OFF(Off)

eRAN





167



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TACAL

G

PORTD

LCACS

W

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to apply DL admission control to a physical

port. If this parameter is set to ON, DL admission

control is applied to the physical port. If this

parameter is set to OFF, DL admission control is not

applied to the physical port.


Unit: None



TACALG TRMULHOCAC

TH

SETTACAL

G

LST

TACAL

G

LOFD-00301101

/

TDLOF

D-00301

101

Transport

Overboo

king

Meaning: Indicates the UL admission threshold for handed-over services. A large value of this parameter

will result in a high UL admission success rate of

handed-over services.


Unit: %


Default Value: 90

TACAL

G

TRMDL

HOCAC

TH

SET

TACAL

GLST

TACAL

G

LOFD-0

0301101

/TDLOF

D-00301

101

Transpo

rt

Overbooking

Meaning: Indicates the DL admission threshold for

handed-over services. A large value of this parameter

will result in a high DL admission success rate of handed-over services.


Unit: %


Default Value: 90

TACAL

G

TRMUL

GOLDC

ACTH

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301101

Transpo

rt

Overboo

king

Meaning: Indicates the UL admission threshold for

new Gold-level services. A large value of this

parameter will result in a high UL admission success

rate of new Gold-level services.


Unit: %


Default Value: 85

eRAN





168



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TACAL

G

TRMDL

GOLDC

ACTH

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


new Gold-level services. A large value of this

parameter will result in a high DL admission success

rate of new Gold-level services.


Unit: %


Default Value: 85

TACAL

G

TRMUL

SILVER

CACTH

SET

TACAL

GLST

TACAL

G

LOFD-0

0301101

/TDLOF

D-00301

101

Transpo

rt

Overbooking


new Silver-level services. A large value of this

parameter will result in a high UL admission successrate of new Silver-level services.


Unit: %


Default Value: 85

TACAL

G

TRMDL

SILVER

CACTH

SET

TACAL

G

LST

TACALG

LOFD-0

0301101

/

TDLOF

D-00301101

Transpo

rt

Overboo

king


new Silver-level services. A large value of this


rate of new Silver-level services.


Unit: %


Default Value: 85

TACAL

G

TRMUL

BRONZ

ECACT

H

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


new Copper-level services. A large value of this

parameter will results in a high UL admission success

rate of new Copper-level services.


Unit: %Actual Value Range: 0~100

Default Value: 85

eRAN





169



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TACAL

G

TRMDL

BRONZ

ECACT

H

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


new Copper-level services. A large value of this


rate of new Copper-level services.


Unit: %


Default Value: 85

TACAL

G

TRMUL

GBRCA

CTH

SET

TACAL

GLST

TACAL

G

LOFD-0

0301101

/TDLOF

D-00301

101

Transpo

rt

Overbooking

Meaning: Indicates the uplink transport admission

threshold for the Guaranteed the Bit Rate (GBR)

service. A large value of this parameter will result in ahigh UL admission success rate of GBR services.


Unit: %


Default Value: 100

TACAL

G

TRMDL

GBRCA

CTH

SET

TACAL

G

LST

TACALG

LOFD-0

0301101

/

TDLOF

D-00301101

Transpo

rt

Overboo

king

Meaning: Indicates the DL admission threshold for the

guaranteed bit rate (GBR) service. A large value of

this parameter will result in a high DL admission

success rate of GBR services.


Unit: %


Default Value: 100

TACAL

G

EMCTA

CPSW

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

LBFD-0

02028 /

TDLBF

D-00202

8

Transpo

rt

Overboo

king

Emerge

ncy Call

Meaning: Indicates the switch that is used to

preferentially admit emergency calls. When this

parameter is set to ON, transmission admission

control is not performed for emergency calls and

emergency calls will be successfully admitted. When

this parameter is set to OFF and the transmission

admission algorithm switch is turned on, transmissionadmission control is performed for emergency calls.

When this parameter is set to OFF and the

transmission admission algorithm switch is turned off,

transmission admission control is not performed for

emergency calls.


Unit: None



eRAN





170



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TOLCA

LG

TRMUL

OLCRE

LTH

SET

TOLCA

LG

LST

TOLCA

LG

LOFD-0

0301103

/

TDLOF

D-00301

103

Transpo

rt

Resourc

e

Overloa

d

Control

Meaning: Indicates the threshold for clearing the UL

OLC. When the UL bandwidth occupancy is below

this threshold, user services are no longer removed.


Unit: %


Default Value: 90

TOLCA

LG

TRMDL

OLCRE

LTH

SET

TOLCA

LG

LSTTOLCA

LG

LOFD-0

0301103

/

TDLOFD-00301

103

Transpo

rt

Resourc

eOverloa

d

Control

Meaning: Indicates the threshold for clearing the DL

OLC. When the DL bandwidth occupancy is below

this threshold, user services are no longer removed.

GUI Value Range: 0~100Unit: %


Default Value: 90

TACAL

G

TRMUL

PRESW

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to enable the UL pre-emption algorithm. If

this parameter is set to ON, the UL pre-emption

algorithm is enabled. In this case, the service with a

higher priority that requests admission may pre-empt

the resources of admitted services with lower

priorities when UL transmission bandwidth isinsufficient. If this parameter is set to OFF, the UL

pre-emption algorithm is disabled. In this case,

services with higher priorities that request admission

cannot pre-empt the resources of admitted services

with lower priorities when UL transmission

bandwidth is insufficient.


Unit: None



eRAN





171



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TACAL

G

TRMDL

PRESW

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to enable the DL pre-emption algorithm. If

this parameter is set to ON, the DL pre-emption

algorithm is enabled. In this case, the service with a

higher priority that requests admission can pre-empt

the resources of admitted services with lower

priorities when DL transmission bandwidth is

insufficient. If this parameter is set to OFF, the DL

pre-emption algorithm is disabled. In this case,

services with higher priorities that request admission

cannot pre-empt the resources of admitted services

with lower priorities when DL transmission

bandwidth is insufficient.GUI Value Range: OFF(Off), ON(On)

Unit: None



TACAL

G

PORTU

LOBSW

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to enable UL overbooking admission control.

It is used to determine the admission bandwidth of the

resource group and facilitate admission control.


Unit: None



TACAL

G

PORTD

LOBSW

SET

TACAL

G

LST

TACAL

G

LOFD-0

0301101

/

TDLOF

D-00301

101

Transpo

rt

Overboo

king


whether to enable DL overbooking admission control.

It is used to determine the admission bandwidth of the

resource group and facilitate admission control.


Unit: None



eRAN





172



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

TXBWA

SW

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301202

/

TDLOF

D-00301

202

Transpo

rt

Dynami

c Flow

Control

Meaning:

Indicates whether to enable the dynamic adjustment of

the RX bandwidth of a transmission resource

group,This parameter takes effect only for the

resource groups to which ENODEBPATH or

GBTSPATH is added.

If this parameter is set to ON, the TX bandwidth is

adjusted according to the network performance and

dynamic bandwidth adjustment parameters (down

speed PLR threshold and down speed delay

threshold). The network performance is monitored

through IP PM sessions, which can be enabled at thelocal end or at the peer end.

If this parameter is set to OFF, the TX bandwidth is

not adjusted.

The UMTS currently does not support this function.


Unit: None



RSCGR PALG

RXBWASW

SETRSCGR

PALG

LST

RSCGR

PALG

LOFD-00301202

/

TDLOF

D-00301

202

Transport

Dynami

c Flow

Control

Meaning:

Indicates whether to enable the dynamic adjustment of

the RX bandwidth of a transmission resource group.

If this parameter is set to ON, the RX bandwidth is

adjusted according to the network performance and

dynamic bandwidth adjustment parameters (down

speed PLR threshold and down speed delay

threshold). The network performance is monitored

through IP PM sessions, which can be enabled at the

local end or at the peer end.

If this parameter is set to OFF, the RX bandwidth isnot adjusted.

The UMTS currently does not support this function.


Unit: None



eRAN





173



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TLDRA

LG

TRMUL

LDRTR

GTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g

Meaning: Indicates the threshold for triggering the UL

high load. If the ratio of the UL transport load to the

UL transport bandwidth of the BS keeps above this

threshold for a period of hysteresis, the UL transport

load of the BS enters the high-load state. In UL high-

load state, the BS sends a UL S1 TNL Load Indicator,

which is set to HighLoad, to each neighboring BS

through the X2 interface.


Unit: %


Default Value: 70

TLDRA

LG

TRMDL

LDRTR

GTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g

Meaning: Indicates the threshold for triggering the DL

high load. If the ratio of the DL transport load to the

DL transport bandwidth of the BS keeps above this

threshold for a period of hysteresis, the DL transport

load of the BS enters the high-load state. In DL high-

load state, the BS sends a DL S1 TNL Load Indicator,

which is set to HighLoad, to each neighboring BS

through the X2 interface.


Unit: %


Default Value: 70

TLDRA

LG

TRMUL

LDRCL

RTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g


high load. If the ratio of the UL transport load to the

UL transport bandwidth of the BS keeps below this

threshold for a period of hysteresis, the UL transport

load of the BS enters the medium-load state. In UL

medium load state, the BS sends a UL S1 TNL Load

Indicator, which is set to MediumLoad, to each

neighboring BS through the X2 interface.


Unit: %


Default Value: 65

eRAN





174



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TLDRA

LG

TRMDL

LDRCL

RTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g


high load. If the ratio of the transport load to the

transmission bandwidth in DL of the BS keeps below

this threshold for a period of time, the DL transport

load of the BS enters the medium-load state. In DL

medium-load state, the BS sends a DL S1 TNL Load

Indicator, which is set to MediumLoad, to each

neighboring BS through the X2 interface.


Unit: %


Default Value: 65

TLDRA

LG

TRMUL

MLDTR

GTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g


medium load. If the ratio of the UL transport load to

the UL transport bandwidth of the BS is above this

threshold, the UL transport load of the BS enters the

medium-load state. In UL medium-load state, the BS

sends a UL S1 TNL Load Indicator, which is set to

MediumLoad, to each neighboring BS through the X2

interface.


Unit: %


Default Value: 50

TLDRA

LG

TRMDL

MLDTR

GTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g

Meaning: Indicates the threshold for triggering the DL

medium load. If the ratio of the DL transport load to

the DL transport bandwidth of the BS is above this

threshold, the DL transport load of the BS enters the

medium-load state. In DL medium-load state, the BS

sends a DL S1 TNL Load Indicator, which is set to

MediumLoad, to each neighboring BS through the X2

interface.


Unit: %


Default Value: 50

eRAN





175



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TLDRA

LG

TRMUL

MLDCL

RTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g


medium load. If the ratio of the UL transport load to

the UL transport bandwidth of the BS is below this

threshold, the UL transport load of the BS enters the

low-load state. In UL low-load state, the BS sends a

UL S1 TNL Load Indicator, which is set to LowLoad,

to each neighboring BS through the X2 interface.


Unit: %


Default Value: 45

TLDRA

LG

TRMDL

MLDCL

RTH

SET

TLDRA

LG

LST

TLDRA

LG

LOFD-0

01032 /

TDLOF

D-00103

2

Intra-

LTE

Load

Balancin

g


medium load. If the ratio of the DL transport load to

the DL transport bandwidth of the BS is below this

threshold, the DL transport load of the BS enters the

low-load state. In DL low-load state, the BS sends a

DL S1 TNL Load Indicator, which is set to LowLoad,

to each neighboring BS through the X2 interface.


Unit: %


Default Value: 45

TOLCA

LG

TRMUL

OLCTR

IGTH

SET

TOLCA

LG

LST

TOLCA

LG

LOFD-0

0301103

/

TDLOF

D-00301

103

Transpo

rt

Resourc

e

Overloa

d

Control


OLC. When the UL bandwidth occupancy reaches the

threshold, low-priority services are removed to

guarantee the quality of high-priority services.


Unit: %


Default Value: 95

TOLCALG

TRMOLCRELB

EARER

NUM

SETTOLCA

LG

LST

TOLCA

LG

LOFD-00301103

/

TDLOF

D-00301

103

Transport

Resourc

e

Overloa

d

Control

Meaning: Indicates the number of released servicesduring an OLC action period.


Unit: None


Default Value: 5

eRAN





176



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TOLCA

LG

TRMUL

OLCSW

ITCH

SET

TOLCA

LG

LST

TOLCA

LG

LOFD-0

0301103

/

TDLOF

D-00301

103

Transpo

rt

Resourc

e

Overloa

d

Control

Meaning: Indicates the UL Over Load Control (OLC)

algorithm switch. In the case of enabled switch, the

bandwidth of the services with low priority would be

released to guarantee the QoS of the services of high

priority when the TX bandwidth changes or during the

overload caused by real-time services.


Unit: None



TOLCALG TRMDLOLCSW

ITCH

SETTOLCA

LG

LST

TOLCA

LG

LOFD-00301103

/

TDLOF

D-00301

103

Transport

Resourc

e

Overloa

d

Control

Meaning: Indicates the switch for the DL OLCalgorithm. If this parameter is set to ON, bandwidth of

the services of a low priority is released to guarantee

the QoS of the services of a high priority when

transport bandwidth changes or overload occurs due to

increased load of non-flow control services.


Unit: None



TOLCALG

TRMDLOLCTR

IGTH

SETTOLCA

LG

LST

TOLCA

LG

LOFD-00301103

/

TDLOF

D-00301

103

Transport

Resourc

e

Overloa

d

Control

Meaning: Indicates the threshold for triggering the DLOLC. When the DL bandwidth occupancy reaches the

threshold, low-priority services are removed to

guarantee the quality of high-priority services.


Unit: %


Default Value: 95

Standard

Qci

UlschPri

orityFac

tor

MOD

STAND

ARDQCI

LST

STAND

ARDQC

I

LOFD-0

0101502

/TDLOF

D-00101

502

LOFD-0

0301102

/

TDLOF

D-00301

102

Dynami

c

Scheduling

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the weight factor used in the

calculation of connection priorities during uplink

scheduling.


Unit: None

Actual Value Range: 0.001~1, step:0.001

Default Value: 700

eRAN





177



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Extende

dQci

UlschPri

orityFac

tor

ADD

EXTEN

DEDQC

I

MOD

EXTEN

DEDQC

I

LST

EXTEN

DEDQC

I

LOFD-0

0101502

/

TDLOF

D-00101

502

LOFD-0

0301102

/

TDLOF

D-00301

102

Dynami

c

Scheduli

ng

Transpo

rt

Differen

tiated

Flow

Control


calculation of connection priorities during uplink

scheduling.


Unit: None


Default Value: 700

RSCGR

PALG

TXSSW SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates whether to enable traffic shaping

for a transmission resource group. If this parameter is

set to ON, traffic shaping is performed according to

the TX bandwidth so that the transmit traffic would

not exceed the capability of downstream routers, thus

avoiding unnecessary packet loss and congestion. If

this parameter is set to OFF, traffic shaping is not

performed during data transmission.


Unit: None



RSCGR

P

TXCBS ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhanced

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the TX committed burst size of a



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,


of 1 Gbit/s TX committed burst size. The UCCU can

be configured with a maximum of 10 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.


Unit: kbit


Default Value: 64

eRAN





178



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

TXEBS ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the TX excessive burst size of a



excessive burst size. The WMPT can be configured

with a maximum of 600 Mbit/s TX excessive burst

size. The UMPT, UMDU or UTRPc can be configured

with a maximum of 1 Gbit/s TX excessive burst size.

The UCCU can be configured with a maximum of 10

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.


Unit: kbit


Default Value: 1000000

RSCGR

P

TXPBS ADD

RSCGR

P

MOD

RSCGR

P

LST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the size of the peak burst

transmitted from the transmission resource group. The

LMPT can be configured with a maximum of 540

Mbit/s TX peak burst size. The UMPT, UMDU or

UTRPc can be configured with a maximum of 1

Gbit/s TX peak burst size. The UCCU can be

configured with a maximum of 10 Gbit/s TX peak burst size. The value of TX peak burst size is set to the

maximum value of TX peak burst size supported by

the board when it bigger than the maximum one.


Unit: kbit


Default Value: None

eRAN





179



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LR CBS SET LR

LST LR

WRFD-

050402

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOFD-00301

102

GBFD-1

18605

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

IP QOS

Meaning: Indicates the Committed Burst Size (CBS)

after rate limitation is configured at a port.The

minimum rate supported by the UMPTb or UMDU is

64 kbit/s.For the GTMU, the value of CBS ranges

from 63 kbit to 256 kbit. If this parameter is set to a

value greater than the maximum allowed value or less

than the minimum allowed value, the maximum or the

minimum allowed value takes effect.


Unit: kbit


Default Value: None

LR EBS SET LR

LST LR

WRFD-

050402

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

GBFD-118605

IP

Transmi

ssion

Introduc

tion onIub

Interface

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

FlowControl

IP QOS

Meaning: Indicates the Excess Burst Size (EBS) after

rate limitation is configured at a port.


Unit: kbit


Default Value: None

eRAN





180



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

PQN SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the number of Priority Queues

(PQs) in a transmission resource group. The queues in

a transmission resource group are classified into PQs

and non-PQs. The scheduling priority of any PQ is

higher than that of any non-PQ. The queues numbered

from 0 to the result after this parameter value minus 1

are PQs. PQ scheduling is used between PQs. A

smaller PQ number indicates a higher scheduling

priority. The queues numbered from this parameter

value to 7 are non-PQs. Weight Round Robin (WPR)

scheduling is used between non-PQs.


Unit: None


Default Value: 3

PRI2QU

E

PRI3 SET

PRI2QU

E

LST

PRI2QU

E

LBFD-0

0300201

/

TDLBF

D-00300

201

DiffServ

QoS

Support

Meaning: Indicates the lowest priority of queue 3. If

the DSCP value of a service packet is smaller than the

PRI2 value but greater than or equal to this parameter

value, the service packet is assigned to queue 3.


Unit: None

Actual Value Range: 0~63Default Value: 24

eRAN





181



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

TCSW SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Meaning:

Indicates whether to enable the backpressure

algorithm of a transmission resource group.

The BS monitors the data buffered in the queues of

each transmission resource group, determines whether

the transmission resource group is congested, and

transmits the backpressure signals (number and

congestion status of the transmission resource group)

to each flow control service.

If the number of data packets in the buffer of any

backpressure queue exceeds 75% of the queue

capacity, the BS regards this transmission resourcegroup as congested and transmits congestion signals.

If the buffered back-pressure packets are less than

50% of the total buffer capacity, the BS decides that

the transmission resource group is not congested. In

this situation, no congestion signal or congestion

release signal is transmitted.

When this parameter is set to ENABLE, both intra-

mode and inter-mode traffic controls are supported.

The inter-mode traffic control for transmission

resource groups applies only to separate-MPT base

stations with co-transmission implemented through

backplane interconnection. However, it does not apply

to cascaded base stations, base stations with co-

transmission implemented through panel

interconnection, or base stations enabled with route

load sharing.

When the inter-mode traffic control function is

enabled for a separate-MPT base station with co-

transmission implemented through backplane

interconnection, the Tunnel Type parameter must be

set to DL(DL) for the tunnel of the mode providingtransmission ports and must be set to UL(UL) for the

tunnel of the mode providing no transmission port.


ENABLE(Enable)

Unit: None


Default Value: ENABLE(Enable)

eRAN





182



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

CTTH SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Overboo

king

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the congestion time threshold of a

transmission resource group. When TCSW is set to

ENABLE, if the buffer time of non-real-time service

data in a transmission resource group exceeds the

threshold, it indicates that the transmission resource

group is congested and the backpressure signals are

transmitted.


Unit: ms


Default Value: 50

RSCGR

PALG

DROPP

KTNU

M

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the number threshold of discarded

packets. This parameter indicates the capability of the

queue in a transmission resource group to buffer

packets. A greater parameter value indicates a

stronger capability. If this parameter is set to 0, the

queue in a transmission resource group cannot buffer

packets, and thus all the delayed packets on the TX

channel are discarded. The number threshold of

discarded packets determines the maximum amount of

data that can be buffered in a transmission resource

group. The congestion time threshold of a

transmission resource group determines the amount of data that is buffered when the transmission resource

group is congested. Ensure that the maximum amount

of data that can be buffered is not less than the amount

of data that is buffered during congestion.


Unit: packet


Default Value: 1000

RSCGR

PALG

CCTTH SET

RSCGR PALG

LST

RSCGR

PALG

LOFD-0

0301101/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rtOverboo

king

Transpo

rt

Differen

tiated

Flow

Control

Meaning: Indicates the congestion clear time

threshold of a transmission resource group. WhenTCSW is set to ENABLE, if the buffer time of non-

real-time service data in a transmission resource group

is below the threshold, it indicates that the

transmission resource group is not congested and

therefore the congestion clear signals are transmitted.


Unit: ms


Default Value: 25

eRAN





183



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

ENodeB

AlgoSwi

tch

TrmSwit

ch

MOD

ENODE

BALGO

SWITC

H

LST

ENODE

BALGO

SWITC

H

LOFD-0

0301102

/

TDLOF

D-00301

102

Transpo

rt

Differen

tiated

Flow

Control

Meaning:

Indicates the switch for uplink flow control over the

air interface. If this switch is on, the scheduling

algorithm is notified to limit the uplink data rate of

UEs in the case of uplink congestion. This method

prevents uplink congestion in the eNodeB, but may

affect fairness and differentiation for combined

services. If this switch is off, the scheduling algorithm

is not notified and therefore no rate restriction is

applied to uplink data from UEs in the case of uplink

congestion. In this case, uplink congestion may occur

in the eNodeB, but fairness and differentiation for

combined services are ensured.

A UE is considered to have combined services if the

UE has two or more flow-controllable non-GBR

bearers. Fairness and differentiation for combined

services of a UE are ensured if the uplink scheduling

algorithm allocates bandwidths to these flow-

controllable non-GBR bearers based on weighting

factors for uplink scheduling priorities

(UlschPriorityFactor). If this switch is on, the

scheduling algorithm is notified to limit the number of

resource blocks (RBs) allocated to the UE in the case

of uplink congestion. According to the relatedspecifications, however, the scheduling algorithm

cannot decide how many RBs to be allocated to each

bearer. The number of RBs that each non-GBR bearer

can use is determined based on the prioritized bit rates

(PBRs) and priorities of the associated logical

channels rather than based on UlschPriorityFactor. As

a result, if this switch is on, fairness and

differentiation for combined services of a UE may be

affected.

GUI Value Range: UlUuFlowCtrlSwitch(UU flow

control switch)

Unit: None

Actual Value Range: UlUuFlowCtrlSwitch

Default Value: UlUuFlowCtrlSwitch:Off

eRAN





184



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

PALG

PLRDT

H

SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301202

/

TDLOF

D-00301

202

Transpo

rt

Dynami

c Flow

Control

Meaning: Indicates the rate downsizing packet loss

rate threshold for bandwidth adjustment. When

RXBWASW or TXBWASW is set to ON, the

estimated available transport bandwidth is reduced if

the packet loss rate detected through IP Performance

Monitoring (IP PM) is higher than this threshold. If

the packet loss rate detected through IP PM is lower

than this threshold, the estimated available transport

bandwidth is increased.


Unit: per mill

Actual Value Range: 0~1000Default Value: 1

RSCGR

PALG

DDTH SET

RSCGR

PALG

LST

RSCGR

PALG

LOFD-0

0301202

/

TDLOF

D-00301

202

Transpo

rt

Dynami

c Flow

Control

Meaning: Indicates the threshold for delay variation

due to rate reduction. When RXBWASW or

TXBWASW is set to ON, the estimated available

transport bandwidth is reduced if the delay variation

detected by an IP PM session is above this

threshold.The UMTS currently does not support this

function.


Unit: ms


Default Value: 50

IPPATH

RT

TRANR

SCTYP

E

ADD

IPPATH

RT

DSP

IPPATH

RT

LST

IPPATHRT

LOFD-0

03016 /

TDLOF

D-00301

6

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the type of transport resource

carried on an IP path route. The value HQ indicates

high-quality transport resources, and the value LQ

indicates low-quality transport resources.

GUI Value Range: HQ(High Quality), LQ(Low

Quality)

Unit: None

Actual Value Range: HQ, LQ

Default Value: None

UDTPA

RAGRP

PRIMP

TLOAD

TH

ADD

UDTPA

RAGRP

MOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

None None Meaning: Indicates the primary port load threshold of

the user data in the hybrid transmission scenario. A

larger value indicates that services are more likely to

be admitted to the primary path.


Unit: %


Default Value: None

eRAN





185



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UDTPA

RAGRP

PRIM2S

ECPTL

OADRA

TH

ADD

UDTPA

RAGRP

MOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

None None Meaning: Indicates the primary-to-secondary port load

ratio threshold of user data in the hybrid transmission

scenario. A smaller value indicates that services are

more likely to be admitted to the primary path.


Unit: %


Default Value: None

Standard

Qci

DlschPri

orityFac

tor

MOD

STAND

ARDQCI

LST

STAND

ARDQC

I

LOFD-0

0101502

/TDLOF

D-00101

502

Dynami

c

Scheduling


calculation of connection priorities during downlink

scheduling.


Unit: None


Default Value: 700

Extende

dQci

DlschPri

orityFac

tor

ADD

EXTEN

DEDQC

I

MOD

EXTEN

DEDQC

I

LST

EXTEN

DEDQC

I

LOFD-0

0101502

/

TDLOF

D-00101

502

Dynami

c

Scheduli

ng


calculation of connection priorities during downlink

scheduling.


Unit: NoneActual Value Range: 0.001~1, step:0.001

Default Value: 700

eRAN





186



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

RSCGR

P

RSCGR

PID

ADD

RSCGR

P

DSP

RSCGR

P

MOD

RSCGR

P

RMV

RSCGR

PLST

RSCGR

P

WRFD-

0213040

6

LOFD-0

03011 /

TDLOF

D-00301

1

GBFD-1

18605

Transmi

ssion

Recours

e

Sharing

on

Iub/Iur

Interface

Enhance

d

Transmi

ssion

QoS

Manage

ment

IP QOS

Meaning: Indicates the ID of a transmission resource

group. When you add a PPP link, an MP group, an

Ethernet port, an Ethernet trunk, a tunnel, or a PPPoE

link, the system automatically creates a corresponding

transmission resource group with Transmission

Resource Group ID set to DEFAULTPORT. When you

remove any of the preceding objects, the system

automatically removes this transmission resource

group.

GUI Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,

13, 14, 15, DEFAULTPORT(Default Port)

Unit: None

Actual Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,

12, 13, 14, 15, DEFAULTPORT

Default Value: None

RSCGR

P

OID ADD

RSCGR

P

LST

RSCGR

P

None None Meaning: Indicates the index of the operator. This

parameter is used to differentiate between operators.

This parameter is reserved for future extension and

does not take effect currently.


Unit: None


Default Value: 0

IPPATH PATHID ADD

IPPATH

DSP

IPPATH

LST

IPPATH

MOD

IPPATH

RMV

IPPATH

WRFD-

050402

GBFD-1

18601

GBFD-1

18611

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abisover IP

Abis IP

over

E1/T1

Meaning: Indicates the ID of an IP path.


Unit: None


Default Value: None

eRAN





187



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IPPATH IPMUX

SWITC

H

ADD

IPPATH

MOD

IPPATH

DSP

IPPATH

LST

IPPATH

WRFD-

050420

GBFD-1

18604

FP

MUX

for IP

Transmi

ssion

Abis

MUX

Meaning: Indicates whether the IPMUX function is

enabled on IP paths. The LTE currently does not

support this function.


ENABLE(Enable)

Unit: None



UDTPA

RAGRP

PRIMT

RANRS

CTYPE

ADD

UDTPA

RAGRPMOD

UDTPA

RAGRP

LST

UDTPA

RAGRP

None None Meaning: Indicates the type of primary transport

resource used to transmit the user date when hybrid

transmission is adopted. HQ indicates that high-quality transport resources are used, while LQ

indicates that low-quality transport resources are used.

When a new service requests admission and admission

control is performed, one of the IP path routes with

transport resources of the same quality is used as the

primary transport path.

GUI Value Range: HQ(High Quality), LQ(Low

Quality)

Unit: None

Actual Value Range: HQ, LQ

Default Value: None

EP2RSC

GRP

ENDPO

INTID

ADD

EP2RSC

GRP

RMV

EP2RSC

GRP

LST

EP2RSC

GRP

WRFD-

050402

GBFD-1

18601

LOFD-0

02004 /

TDLOF

D-00200

4

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abis

over IP

Self-

configur

ation

Meaning: Indicates the end point group or user plane

peer that needs to be added to the specified

transmission resource group.


Unit: None


Default Value: None

eRAN





188



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

EP2RSC

GRP

RSCGR

PID

ADD

EP2RSC

GRP

RMV

EP2RSC

GRP

LST

EP2RSC

GRP

WRFD-

050402

GBFD-1

18601

LOFD-0

02004 /

TDLOF

D-00200

4

IP

Transmi

ssion

Introduc

tion on

Iub

Interface

Abis

over IP

Self-

configur

ation

Meaning: Indicates the ID of the transmission

resource group to which a node maps.


Unit: None


Default Value: None

IPPATH

RT

SRCIP ADD

IPPATH

RT

DSP

IPPATH

RT

RMV

IPPATH

RT

LSTIPPATH

RT

LOFD-0

03016 /

TDLOF

D-00301

6

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the source IP address of an IP path

route. The source IP address must be the same as the

configured device IP address.


Unit: None


Default Value: None

IPPATH

RT

DSTIP ADD

IPPATH

RT

DSP

IPPATH

RT

RMV

IPPATH

RT

LST

IPPATH

RT

LOFD-0

03016 /

TDLOF

D-00301

6

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the destination IP address of an IP

path route.


Unit: None


Default Value: None

eRAN





189



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

IPPATH

RT

NEXTH

OPIP

ADD

IPPATH

RT

DSP

IPPATH

RT

LST

IPPATH

RT

LOFD-0

03016 /

TDLOF

D-00301

6

Differen

t

Transpo

rt Paths

based on

QoS

Grade

Meaning: Indicates the next hop IP address of an IP

path route. The next hop IP address and the

configured device IP address must be on the same

network segment, but cannot be the same.


Unit: None


Default Value: None

LR LRSW SET LR

LST LR

WRFD-

050402

LOFD-0

0301101

/

TDLOF

D-00301

101

LOFD-0

0301102

/

TDLOF

D-00301

102

GBFD-1

18605

IP

Transmi

ssionIntroduc

tion on

Iub

Interface

Transpo

rt

Overboo

king

Transpo

rt

Differentiated

Flow

Control

IP QOS

Meaning: Indicates the switch for limiting the line rate

at the port.


ENABLE(Enable)

Unit: None



PRI2QU

E

PRI0 SET

PRI2QU

E

LST

PRI2QU

E

LBFD-0

0300201

/

TDLBF

D-00300

201

DiffServ

QoS

Support


the Differentiated Services Code Point (DSCP) value

of a service packet is greater than or equal to this

parameter value, the service packet is assigned to

queue 0.

GUI Value Range: 0~63Unit: None


Default Value: 48

eRAN





190



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

PRI2QU

E

PRI1 SET

PRI2QU

E

LST

PRI2QU

E

LBFD-0

0300201

/

TDLBF

D-00300

201

DiffServ

QoS

Support






Unit: None


Default Value: 40

PRI2QU

E

PRI2 SET

PRI2QU

ELST

PRI2QU

E

LBFD-0

0300201

/TDLBF

D-00300

201

DiffServ

QoS

Support



PRI1 value but greater than or equal to this parameter value, the service packet is assigned to queue 2.


Unit: None


Default Value: 32

PRI2QU

E

PRI4 SET

PRI2QU

E

LST

PRI2QUE

LBFD-0

0300201

/

TDLBF

D-00300201

DiffServ

QoS

Support






Unit: None


Default Value: 16

PRI2QU

E

PRI5 SET

PRI2QU

E

LST

PRI2QU

E

LBFD-0

0300201

/

TDLBF

D-00300

201

DiffServ

QoS

Support






Unit: NoneActual Value Range: 0~63

Default Value: 8

eRAN





191



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

PRI2QU

E

PRI6 SET

PRI2QU

E

LST

PRI2QU

E

LBFD-0

0300201

/

TDLBF

D-00300

201

DiffServ

QoS

Support






Unit: None


Default Value: 0

eNodeB

Path

IpPathId ADD

ENODE

BPATHLST

ENODE

BPATH

MOD

ENODE

BPATH

RMV

ENODE

BPATH

LBFD-0

0300101

/TDLBF

D-00300

101

LBFD-0

0300102

/

TDLBF

D-00300

102

LBFD-0

0300103

/

TDLBF

D-00300

103

LOFD-0

01018 /

TDLOF

D-00101

8

Star

Topolog

yChain

Topolog

y

Tree

Topolog

y

S1-flex

Meaning: Indicates the ID of the IP path.


Unit: None


Default Value: None

eRAN





192



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

eNodeB

Path

AppTyp

e

ADD

ENODE

BPATH

MOD

ENODE

BPATH

LST

ENODE

BPATH

LBFD-0

0300101

/

TDLBF

D-00300

101

LBFD-0

0300102

/

TDLBF

D-00300

102

LBFD-0

0300103

/

TDLBF

D-00300

103

LOFD-0

01018 /

TDLOF

D-00101

8

Star

Topolog

y

Chain

Topolog

y

Tree

Topolog

y

S1-flex

Meaning: Indicates the application type of the IP path.

GUI Value Range: S1(S1), X2(X2)

Unit: None

Actual Value Range: S1, X2

Default Value: None

eNodeB

Path

S1Interf

aceId

ADD

ENODE

BPATH

MOD

ENODE

BPATH

LST

ENODE

BPATH

LBFD-0

0300101

/

TDLBF

D-00300

101

LBFD-0

0300102

/

TDLBF

D-00300

102

LBFD-0

0300103

/

TDLBF

D-00300

103

LOFD-0

01018 /

TDLOF

D-00101

8

Star

Topolog

y

Chain

Topolog

y

Tree

Topolog

y

S1-flex

Meaning: Indicates the S1 interface ID of the IP path.

This parameter is unavilable in this version, it is

recommended to be set as 0.


Unit: None


Default Value: None

eRAN





193



11 Counters

Table 11-1 Counters

Counter ID Counter Name CounterDescription

Feature ID Feature Name

1526728284 L.E-

RAB.AbnormRel.C

ong

Number of

abnormal releases

of activated E-

RABs due to

network congestion

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

Congestion Control

Congestion Control

Radio/transport

resource pre-emption

Radio/transport

resource pre-

emption

1526728444 L.Cell.UserLimit.Pr

eEmp.Num

Number of

successful

preemptions

triggered due to

user limitation

Multi-mode: None

GSM: None

UMTS: None

LTE:

LOFD-00102901

TDLOFD-0010290

1

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

eRAN


Description 11 Counters



194





1526729495 L.E-

RAB.AbnormRel.C

ong.PLMN

Number of

abnormal releases

of activated E-

RABs because of

network congestion

for a specific

operator

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Radio Bearer

Management

Radio Bearer

Management

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

Hybrid RAN

Sharing

1526729912 L.E-

RAB.AbnormRel.C

ong.PreEmp

Number of

abnormal releases

of activated E-

RABs because of

radio resource

preemption

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

eRAN





195





1526729923 L.E-

RAB.AbnormRel.C

ong.VoIP

Number of

abnormal releases

of activated E-

RABs for voice

services because of

radio network

congestion

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

1526729926 L.E-

RAB.AbnormRel.C

ong.PreEmp.VoIP

Number of

abnormal releases

of activated E-

RABs for voice

services because of

radio resource

preemption

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transportresource pre-

emption

eRAN





196





1526729931 L.E-

RAB.AbnormRel.C

ong.PreEmp.PLMN

Number of

abnormal releases

of activated E-

RABs because of

radio resource

preemption for a

specific operator

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

Hybrid RAN

Sharing

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

eRAN





197





1526729942 L.E-

RAB.AbnormRel.C

ong.VoIP.PLMN

Number of

abnormal releases

of activated E-

RABs for voice

services because of

radio network

congestion for a

specific operator

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

Hybrid RAN

Sharing

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

eRAN





198





1526729947 L.E-

RAB.AbnormRel.C

ong.PreEmp.VoIP.P

LMN

Number of

abnormal releases

of activated E-

RABs for voice

services because of

radio resource

preemption for a

specific operator

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002008

TDLBFD-002008

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

LBFD-002024

TDLBFD-002024

LOFD-00102901

TDLOFD-0010290

1

Radio Bearer

Management

Radio Bearer

Management

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

RAN Sharing with

Common Carrier

RAN Sharing with

Dedicated Carrier

Hybrid RAN

Sharing

Congestion Control

Congestion Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

1526736866 L.Cell.UserSpec.Pr

epEmp.PrepAtt.Nu

m

Number of times

preemptions are

triggered by the

limitation of the UE

number

specification

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002023

TDLBFD-002023

LOFD-00102901

TDLOFD-0010290

1

Admission Control

Admission Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

eRAN





199





1526736867 L.Cell.UserLic.Lim

it.Num.PLMN

Number of times

the licensed number

of UEs is limited

for a specific

operator

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002023

TDLBFD-002023

LOFD-00102901

TDLOFD-0010290

1

LOFD-001036

LOFD-070206TDLOFD-001036

Admission Control

Admission ControlRadio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

RAN Sharing with

Common Carrier

Hybrid RAN

Sharing

RAN Sharing with

Common Carrier

1526736868 L.Cell.UserLic.Prep

Emp.Succ.Num.PL

MN

Number of

successful

preemptions

triggered by the

limitation of the

licensed number of

UEs for a specific

operator

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002023

TDLBFD-002023

LOFD-00102901

TDLOFD-0010290

1

LOFD-001036

LOFD-070206

TDLOFD-001036

Admission Control

Admission Control

Radio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

RAN Sharing with

Common Carrier

Hybrid RAN

Sharing

RAN Sharing with

Common Carrier

1526736869 L.Cell.UserLic.Lim

it.Num

Number of times

the licensed number

of UEs is limited

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-002023

TDLBFD-002023

LOFD-00102901

TDLOFD-0010290

1

Admission Control

Admission Control

Radio/transport

resource pre-emption

Radio/transport

resource pre-

emption

eRAN





200





1526736870 L.Cell.UserLic.Prep

Emp.Succ.Num

Number of

successful

preemptions

triggered by the

limitation of the

licensed number of

UEs

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002023

TDLBFD-002023

LOFD-00102901

TDLOFD-0010290

1

Admission Control

Admission ControlRadio/transport

resource pre-

emption

Radio/transport

resource pre-

emption

1542455365 VS.RscGroup.TxBy

tes

Number of bytes in

the packets

successfullytransmitted by the

resource group

Multi-mode: None

GSM:GBFD-118605

UMTS:

WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP TransmissionIntroduction on Iub

Interface

Enhanced Transport

QoS Management

Enhanced Transport

QoS Management

1542455367 VS.RscGroup.TxPk

ts

Number of packets

successfully

transmitted by the

resource group

Multi-mode: None

GSM:

GBFD-118605

UMTS:WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP Transmission

Introduction on Iub

InterfaceEnhanced Transport

QoS Management

Enhanced Transport

QoS Management

1542455369 VS.RscGroup.TxDr

opBytes

Number of bytes in

the packets

discarded by the

resource group due

to transmission

failures

Multi-mode: None

GSM:

GBFD-118605

UMTS:

WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP Transmission

Introduction on Iub

Interface

Enhanced Transport

QoS Management

Enhanced Transport

QoS Management

eRAN





201





1542455371 VS.RscGroup.TxDr

opPkts

Number of packets

discarded by the

resource group due

to transmission

failures

Multi-mode: None

GSM:GBFD-118605

UMTS:

WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP TransmissionIntroduction on Iub

Interface

Enhanced Transport

QoS Management

Enhanced Transport

QoS Management

1542455375 VS.RscGroup.TxM

axSpeed

Maximum transmit

rate of the resource

group

Multi-mode: None

GSM:

GBFD-118605

UMTS:WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP Transmission

Introduction on Iub

Interface

Enhanced Transport

QoS Management

Enhanced Transport

QoS Management

1542455376 VS.RscGroup.TxMi

nSpeed

Minimum transmit


group

Multi-mode: None

GSM:

GBFD-118605

UMTS:

WRFD-050402

LTE:

LOFD-003011

TDLOFD-003011

IP QOS

IP Transmission

Introduction on Iub

Interface

Enhanced TransportQoS Management

Enhanced Transport

QoS Management

1542455377 VS.RscGroup.TxM

eanSpeed

Average transmit


group

Multi-mode: None

GSM:

GBFD-118605

UMTS:

WRFD-050402

LTE:

LOFD-003011TDLOFD-003011

IP QOS

IP Transmission

Introduction on Iub

Interface

Enhanced Transport

QoS Management

Enhanced TransportQoS Management

eRAN





202



12 Glossary

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

eRAN


Description 12 Glossary



203



13 Reference Documents

1. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved

eRAN


Description 13 Reference Documents