Scheduling (eRAN3.0 06)

Scheduling
eRAN3.0
Feature Parameter Description
Issue 06
Date 2013-05-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
eRAN
Scheduling Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
2.1 Introduction.................................................................................................................................... 2-1
2.2 Features Involved in Scheduling ................................................................................................... 2-1
2.3 Benefits ......................................................................................................................................... 2-2
2.3.1 DL Basic Scheduling............................................................................................................. 2-2
2.3.2 DL Enhanced Scheduling ..................................................................................................... 2-3
2.3.3 UL Basic Scheduling............................................................................................................. 2-4
2.3.4 UL Enhanced Scheduling ..................................................................................................... 2-4
3 DL Basic Scheduling................................................................................................................3-1
3.1 Introduction.................................................................................................................................... 3-1
3.1.1 Inputs .................................................................................................................................... 3-2
3.1.2 Basic Functions .................................................................................................................... 3-3
3.1.3 Outputs ................................................................................................................................. 3-3
3.1.4 Procedure for DL Scheduling in Each TTI ............................................................................ 3-3
3.2 Scheduling Common Control Information ..................................................................................... 3-4
3.3 Scheduling for DL Retransmissions .............................................................................................. 3-5
3.4 DL Basic Scheduling for Initial Transmissions .............................................................................. 3-5
3.4.1 Obtaining DL Scheduling Resources .................................................................................... 3-6
3.4.2 Selecting UEs for DL Scheduling ......................................................................................... 3-7
3.4.3 Determining MCSs for DL Scheduling .................................................................................. 3-8
3.4.4 Determining the Number of RBs for DL Scheduling ............................................................. 3-9
3.5 CSI Reporting ................................................................................................................................ 3-9
4 DL Enhanced Scheduling .......................................................................................................4-1

4.1 DL CQI Adjustment ........................................................................................................................ 4-1
4.2 DL Dynamic Scheduling ................................................................................................................ 4-2
4.2.1 Calculating the Priority of GBR Services .............................................................................. 4-2
4.2.2 Calculating the Priority of Non-GBR Services ...................................................................... 4-2
5 UL Basic Scheduling................................................................................................................5-1
5.1 Introduction.................................................................................................................................... 5-1
5.1.1 Inputs .................................................................................................................................... 5-2
5.1.2 Basic Functions .................................................................................................................... 5-2
5.1.3 Outputs ................................................................................................................................. 5-3
5.1.4 Procedure for UL Scheduling in Each TTI ............................................................................ 5-3
5.2 UL Dynamic Scheduling for Retransmissions ............................................................................... 5-4
Issue 06 (2013-05-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Scheduling Contents
5.3 UL Dynamic Scheduling for Initial Transmissions ......................................................................... 5-5

5.3.1 Obtaining UL Scheduling Resources .................................................................................... 5-5
5.3.2 Selecting UEs for UL Scheduling ......................................................................................... 5-6
5.3.3 Determining MCSs for UL Scheduling .................................................................................. 5-6
5.3.4 Determining the Number of RBs for UL Scheduling ............................................................. 5-7
6 UL Enhanced Scheduling .......................................................................................................6-1

6.1 UL 64QAM ..................................................................................................................................... 6-1
6.2 TTI Bundling .................................................................................................................................. 6-1
6.3 UL QoS Management .................................................................................................................... 6-2
6.4 Preallocation Scheduling ............................................................................................................... 6-3
7 Cooperation with Other Features .........................................................................................7-1

7.1 Scheduling in RAN Sharing Mode................................................................................................. 7-1
8 Related Features and Their Impacts on the Network ......................................................8-1

8.1 Scheduling Feature Selection Principles ...................................................................................... 8-1
8.2 DL Scheduling ............................................................................................................................... 8-1
8.2.1 Required Features ................................................................................................................ 8-1
8.2.2 Mutually Exclusive Features ................................................................................................. 8-1
8.2.3 Affected Features ................................................................................................................. 8-1
8.2.4 Impact on the Network .......................................................................................................... 8-1
8.3 UL Scheduling ............................................................................................................................... 8-2
8.3.1 Required Features ................................................................................................................ 8-2
8.3.2 Mutually Exclusive Features ................................................................................................. 8-2
8.3.3 Affected Features ................................................................................................................. 8-2
8.3.4 Impact on the Network .......................................................................................................... 8-2
9 Engineering Guidelines for DL Basic Scheduling ...........................................................9-1

9.1 When to Use Scheduling ............................................................................................................... 9-1
9.1.1 LBFD-002025 Basic Scheduling .......................................................................................... 9-1
9.2 Information to Be Collected ........................................................................................................... 9-1
9.3 Network Planning .......................................................................................................................... 9-1
9.4 Deploying Basic Scheduling Policies ............................................................................................ 9-1
9.4.1 Deployment Requirements ................................................................................................... 9-1
9.4.2 Data Preparation................................................................................................................... 9-2
9.4.3 Precautions ........................................................................................................................... 9-2
9.4.4 Initial Configuration ............................................................................................................... 9-3
9.4.5 Activation Observation .......................................................................................................... 9-3
9.5 Performance Optimization ........................................................................................................... 9-10
9.6 Troubleshooting ........................................................................................................................... 9-10
10 Engineering Guidelines for DL Enhanced Scheduling ...............................................10-1

10.1 When to Use Scheduling ........................................................................................................... 10-1
10.1.1 LOFD-00101501 CQI Adjustment .................................................................................... 10-1
Issue 06 (2013-05-20) Huawei Proprietary and Confidential ii

eRAN
Scheduling Contents
10.1.2 LOFD-00101502 Dynamic Scheduling ............................................................................. 10-1

10.2 Information to Be Collected ....................................................................................................... 10-1
10.3 Network Planning ...................................................................................................................... 10-1
10.4 Deploying CQI Adjustment ........................................................................................................ 10-1
10.4.1 Deployment Requirements ............................................................................................... 10-1
10.4.2 Data Preparation .............................................................................................................. 10-2
10.4.3 Precautions ....................................................................................................................... 10-3
10.4.4 Initial Configuration ........................................................................................................... 10-3
10.4.5 Activation Observation ...................................................................................................... 10-3
10.5 Deploying the Dynamic Scheduling .......................................................................................... 10-4
10.5.3 Precautions ....................................................................................................................... 10-7
10.6 Performance Optimization ......................................................................................................... 10-9
10.7 Troubleshooting ......................................................................................................................... 10-9
11 Engineering Guidelines for UL Basic Scheduling .......................................................11-1

11.1.1 LBFD-002025 Basic Scheduling ....................................................................................... 11-1
11.4 Deploying Basic Scheduling Policies ........................................................................................ 11-1
11.4.2 Data Preparation ............................................................................................................... 11-1
11.4.3 Precautions ....................................................................................................................... 11-2
11.5 Performance Optimization ......................................................................................................... 11-8
11.6 Troubleshooting ......................................................................................................................... 11-8
12 Engineering Guidelines for UL Enhanced Scheduling ...............................................12-1

12.1.1 LOFD-001006 UL 64QAM ................................................................................................ 12-1
12.1.2 LOFD-00101502 Dynamic Scheduling ............................................................................. 12-1
12.1.3 LOFD-001048 TTI Bundling ............................................................................................. 12-1
12.4 Deploying UL 64QAM ................................................................................................................ 12-1
12.4.3 Precautions ....................................................................................................................... 12-2
Issue 06 (2013-05-20) Huawei Proprietary and Confidential iii

eRAN
Scheduling Contents

12.5 Deploying the Dynamic Scheduling .......................................................................................... 12-5
12.5.3 Precautions ....................................................................................................................... 12-9
12.5.5 Activation Observation .................................................................................................... 12-10
12.6 Deploying TTI Bundling ........................................................................................................... 12-14
12.6.1 Deployment Requirements ............................................................................................. 12-14
12.6.2 Data Preparation ............................................................................................................ 12-15
12.6.3 Precautions ..................................................................................................................... 12-15
12.6.4 Initial Configuration ......................................................................................................... 12-16
12.6.5 Activation Observation .................................................................................................... 12-16
12.7 Performance Optimization ....................................................................................................... 12-17
12.8 Troubleshooting ....................................................................................................................... 12-17
13 Parameters .............................................................................................................................13-1
14 Counters..................................................................................................................................14-1
15 Glossary ..................................................................................................................................15-1
16 Reference Documents .........................................................................................................16-1
Issue 06 (2013-05-20) Huawei Proprietary and Confidential iv

eRAN
Scheduling 1 Introduction
1 Introduction
1.1 Scope
The Long Term Evolution (LTE) system adopts shared-channel transmissions in which time-frequency
resources are dynamically shared by user equipment (UEs). E-UTRAN NodeBs (eNodeBs) perform
scheduling to allocate time-frequency resources for uplink (UL) and downlink (DL) transmissions.
This document describes the eNodeB features related to scheduling in terms of the implementation,
parameters involved, feature relationships, network impact, and engineering guidelines.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
1.2 Intended Audience

This document is intended for:
 Personnel who need to understand scheduling
 Personnel who work with Huawei LTE products
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change: refers to a change in the scheduling feature of a specific product version.
 Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.
Document Issues
The document issues are as follows:
 06 (2013-05-20)
 05 (2012-12-29)
 04 (2012-09-20)
 03 (2012-06-30)
 02 (2012-05-11)
 01 (2012-03-30)
 Draft A (2012-01-10)
06 (2013-05-20)
Compared with issue 05(2012-12-29), issue 06 (2013-05-20) includes the following changes.
Change Change Description Parameter Change

Type
Feature None None
change
Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-1

eRAN

Type
Editorial Optimized the document organization. None
change
05 (2012-12-29)
Compared with issue 04 (2012-09-20), issue 05 (2012-12-29) includes the following changes.

Type
Feature None None
change
Editorial Added the description that the enabling and disabling of TTI None
change bundling are triggered by RRC messages. For details, see
section 6.2 "TTI Bundling" and section 8.3.4 "Impact on the
Network."
04 (2012-09-20)

Type
Feature None None
change
Editorial Added descriptions of StepVarySwitch under the Added StepVarySwitch under
change CellAlgoSwitch.CqiAdjAlgoSwitch parameter. For the
details, see section 4.1 "DL CQI Adjustment." CellAlgoSwitch.CqiAdjAlgoS
witch parameter.
Modified the definition of the CQI. For details, see None
section 3.1.1 "Inputs."
Modified the PBR configuration principle for GBR
services and non-GBR services. For details, see
Table 6-1.
Revised some descriptions in the following sections: None
 5.2 "UL Dynamic Scheduling for Retransmissions."
 6.3 "UL QoS Management"
 6.4 "Preallocation Scheduling"
 3.5 "CSI Reporting"
 9.4.2 "Data Preparation."
Optimized Figure 3-1"DL scheduling" and Figure 5-1 None
"UL scheduling".

eRAN

Type
Revised descriptions of activation observation for TTI None
bundling. For details, see section 12-16"Activation
Observation."
03 (2012-06-30)
Change Type Change Description Parameter Change

Feature change Modified the UE-level CQI period configuration. For Added the following
details, see section 10.4 "Deploying CQI Adjustment." parameters:
 CqiPeriodAdaptive
 UserCqiPeriodCfg
Editorial change Modified descriptions in the following sections: None
 3.4.1 "Obtaining DL Scheduling Resources"
 4.1 "DL CQI Adjustment"
 5.3.1 "Obtaining UL Scheduling Resources"
 6.3 "UL QoS Management"
 3.5 "CSI Reporting"
02 (2012-05-11)

Feature change None None
Editorial change Deleted descriptions of the feature LOFD-001016 None
VoIP Semi-persistent Scheduling. For details about
the feature, see VoIP Feature Parameter Description.
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.

Feature change None None
Editorial change Optimized the document organization. None

eRAN
Draft A (2012-01-10)
This is a draft.
Compared with issue 02 (2011-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.

Feature change Added the support of aperiodic channel state None
information (CSI) reporting. For details, see section
3.5 "CSI Reporting."
Editorial change  Optimized the document organization. None
 Added chapter 8 "Related Features and Their
Impacts on the Network."

eRAN
Scheduling 2 Overview
2 Overview
2.1 Introduction
A scheduler in an eNodeB mainly allocates appropriate system resources to UEs in each cell so that the
UEs can transmit and receive data. This kind of resource allocation is one of the major functions of the
LTE system, in which all UEs in a cell share the channels and other resources in the cell. Huawei
schedulers are designed to trade off between single-UE performance and overall network capacity and
also provide end-to-end quality of service (QoS) management solutions for better QoS.
The schedulers are located above the physical layer. Its basic function is to allocate time-frequency
resources to UEs in each subframe for uplink and downlink transmissions. The minimum scheduling unit
consists of 12 subcarriers (spanning 180 kHz in the frequency domain) and 1 subframe (lasting 1 ms in
the time domain), as shown in Figure 2-1.
Figure 2-1 Minimum scheduling unit
One UE can be allocated multiple resource blocks (RBs) in each transmission time interval (TTI). The
maximum number of available RBs in the frequency domain in a cell depends on the cell bandwidth, as
listed in Table 2-1.
Table 2-1 Number of available RBs per bandwidth
Bandwidth (MHz) 1.4 3.0 5.0 10.0 15.0 20.0
Number of Available RBs 6 15 25 50 75 100
2.2 Features Involved in Scheduling

Scheduling features are classified into basic scheduling features and enhanced scheduling features, as
listed in Table 2-2.

eRAN
Table 2-2 Features involved in scheduling

UL or DL Basic or Feature Name
Optional
DL Basic LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
LBFD-001006 AMC
LBFD-002005 DL Asynchronous HARQ
LBFD-002025 Basic Scheduling
LBFD-002031 Support of Aperiodic CQI Reports
Optional LOFD-00101501 CQI Adjustment
LOFD-00101502 Dynamic Scheduling
UL Basic LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
LBFD-001006 AMC
LBFD-002006 UL Synchronous HARQ
Optional LOFD-001006 UL 64QAM
LOFD-001048 TTI Bundling
 For details about basic features in downlink scheduling, see 3 DL Basic Scheduling.
 For details about optional features in downlink scheduling, see 4 DL Enhanced Scheduling.
 For details about basic features in uplink scheduling, see 5 UL Basic Scheduling.
 For details about optional features in uplink scheduling, see 6 UL Enhanced Scheduling.
2.3 Benefits
2.3.1 DL Basic Scheduling
LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
In accordance with 3GPP TS 36.211 Release 9 issued in March 2010, this basic feature allows eNodeBs
to use different modulation schemes among DL and UL QPSK, DL and UL 16QAM, and DL 64QAM
under different channel conditions. The modulation schemes are characterized as follows:
 Quadrature phase shift keying (QPSK) modulates two bits onto one modulation symbol.
 16QAM modulates four bits onto one modulation symbol.
 64QAM modulates six bits onto one modulation symbol.
NOTE
QAM is short for quadrature amplitude modulation.

eRAN
A higher modulation order (more bits per modulation symbol) helps achieve higher transmission
efficiency but requires higher signal-to-interference-plus-noise ratio (SINR) in order to maintain the block
error rate (BLER).
As an example, if channel conditions are favorable, the high-order modulation scheme DL 64QAM is
used to increase overall throughput and spectral efficiency.
LBFD-001006 AMC
This basic feature adaptively selects an optimal modulation and coding scheme (MCS) based on
channel quality to increase overall spectral efficiency. In adaptive modulation and coding (AMC):
 The optimal MCS for uplink transmissions is selected based on the SINR measured by each eNodeB.
 The optimal MCS for downlink transmissions is selected based on the channel quality indicator (CQI)
reported by each UE.
LBFD-002005 DL Asynchronous HARQ

This is a basic feature. Compared with automatic repeat request (ARQ), DL asynchronous hybrid ARQ
(HARQ) is a fast-retransmission mechanism implemented at the Media Access Control (MAC) and
physical layers. If a UE incorrectly decodes a packet, a negative acknowledgment (NACK) is sent to the
eNodeB to request retransmission of the packet. The retransmitted data is soft-combined with the
previously received data to improve decoding performance. DL asynchronous HARQ uses the
incremental redundancy (IR) algorithm. This feature increases the DL throughput of UEs and reduces DL
transmission latency. It uses the following techniques:
 Determining transmission time
 Determining resource positions
 Determining the MCS

This is a basic feature that addresses the following basic scheduling algorithms for both the UL and DL:
 Maximum carrier-to-interference ratio (Max C/I)
 Round robin (RR)
 Proportional fair (PF)
Operators can select one from the algorithms as required.
LBFD-002031 Support of Aperiodic CQI Reports

This is a basic feature that addresses the support of eNodeBs for aperiodic CQI reporting from UEs.
In the current version, the eNodeB supports only aperiodic CQI reporting of the "Higher
Layer-configured" type. Aperiodic CQI reporting is triggered by the uplink scheduler, which notifies UEs
of aperiodic CQI reporting through the CQI Request field in the UL Grant message.
2.3.2 DL Enhanced Scheduling

LOFD-00101501 CQI Adjustment
This optional feature increases system throughput as follows:
 A closed-loop mechanism is used to dynamically compensate for inaccurate CQIs reported by UEs,
which optimizes MCS selection and increases overall throughput.

eRAN
 The CQI measurement and reporting modes are adaptively selected to suit the scenario at hand to
increase system throughput. For details about the reporting modes, see section 7.2 in 3GPP TS
36.213 V9.3.0 (2010-09).

This optional feature offers the following benefits:
 Helps meet QoS requirements of services with various QoS class identifiers (QCIs).
 Provides differentiated service for UEs.
 Helps achieve an optimal tradeoff between transmission fairness across UEs and cell throughput while
meeting QoS requirements.
2.3.3 UL Basic Scheduling

For details about the benefits of LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM,
LBFD-001006 AMC, and LBFD-002025 Basic Scheduling, see 2.3.1 DL Basic Scheduling.
LBFD-002006 UL Synchronous HARQ

This is a basic feature. UL synchronous HARQ is also a fast-retransmission mechanism implemented at
the MAC and physical layers. This feature increases the UL throughput of UEs and reduces UL
transmission latency. The default mode for the UL is synchronous non-adaptive HARQ. It automatically
switches to synchronous adaptive HARQ when certain conditions are met. In synchronous non-adaptive
HARQ, the transport block size (TBS), and MCS for each retransmission are identical to those for the
initial transmission. In synchronous adaptive HARQ, the transmission time, TBS, and MCS for
retransmissions are adaptively determined by each eNodeB.
UL synchronous HARQ uses the following techniques:
 Automatically switching between adaptive and non-adaptive modes
 Determining the resource position and TBS in adaptive mode
 Determining the MCS in adaptive mode
2.3.4 UL Enhanced Scheduling

For details about the benefits of LOFD-00101502 Dynamic Scheduling, see 2.3.2 DL Enhanced
Scheduling.
LOFD-001006 UL 64QAM
This optional feature is an enhancement of UL modulation. UL 64QAM further increases UL spectral
efficiency and cell throughput and improves user experience when channel quality is favorable.
LOFD-001048 TTI Bundling

This optional feature enables several consecutive subframes to transmit the same data block. The
bundled TTIs are regarded as one unit of resource. TTI bundling is used only to improve PUSCH edge
coverage for VoIP services.
TTI bundling is not supported in a cell with 1.4 MHz bandwidth.

eRAN
Scheduling 3 DL Basic Scheduling
3 DL Basic Scheduling
3.1 Introduction
In the LTE system, DL scheduling is performed at the MAC layer. DL scheduling allocates resources on
the physical DL shared channel (PDSCH) for UEs and selects appropriate MCSs for the transmission of
system information and user data.
Figure 3-1 shows the inputs, outputs, and basic functions of DL scheduling.
Figure 3-1 DL scheduling
RI: rank indication PMI: precoding matrix indication

MIMO: multiple-input multiple-output
DL basic scheduling involves the following features:

 LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
 LBFD-001006 AMC
 LBFD-002005 DL Asynchronous HARQ
 LBFD-002025 Basic Scheduling
 LBFD-002031 Support of Aperiodic CQI Reports
For details about the preceding features, see sections in this chapter.
DL enhanced scheduling involves the following features:
 LOFD-00101501 CQI Adjustment
 LOFD-00101502 Dynamic Scheduling
For details about the preceding features, see 4 DL Enhanced Scheduling.

eRAN
3.1.1 Inputs
UE Capability
Section 4.1 in 3GPP TS 36.306 Release10 issued in March 2011 specifies eight UE categories and the
maximum numbers of bits and layers that can be transmitted in each TTI for each UE category.
Channel State Information

A scheduler schedules UEs and allocates resources to UEs based on the channel state information
(CSI), which includes the rank indication (RI), precoding matrix indication (PMI), and CQI.
The RI, PMI, and CQI are estimated based on the instantaneous DL channel quality by the UE.
Huawei eNodeBs support aperiodic CSI reporting (addressed by LBFD-002031 Support of aperiodic
reports) and determine whether to use periodic or aperiodic CSI reporting. For details, see section 3.5
"CSI Reporting."
 RI
In spatial multiplexing transmission mode, UEs report RIs to the eNodeB, providing information about
the channel ranks recommended to the DL scheduler for DL transmissions.
 PMI
In closed-loop spatial multiplexing transmission mode, UEs report PMIs to the eNodeB,
recommending precoding matrices to the DL scheduler.
 CQI
UEs also report CQIs to the eNodeB, providing information about DL channel quality that the DL
scheduler can use for link adaptation.
TX Power
The DL transmit (TX) power is shared by all UEs in a cell. According to 3GPP Release 8, DL TX power is
determined by the cell-specific reference signal (RS) energy per resource element (EPRE), PA, and PB.
The eNodeB sends UEs the information element (IE) PDSCH-ConfigCommon that contains cell-specific
RS EPRE and PB, and the IE PDSCH-ConfigDedicated that contains PA. For details about PA and PB,
see 3GPP TS 36.213.
HARQ Feedback
ACK and NACK feedback is another input to the scheduler. The feedback indicates whether data is
successfully transmitted or retransmitted. HARQ retransmissions implemented by Huawei eNodeBs
always have a high scheduling priority, though the priority of signaling transmission and that of
semi-persistent transmission are still higher.
QoS Requirements
QoS requirements of service bearers are sent to the eNodeB from the evolved packet core (EPC)
through S1 Application Protocol (S1-AP) signaling. The QoS profile of an LTE bearer consists of ARP,
QCI, GBR, MBR (for GBR services), and AMBR (for non-GBR services).
NOTE
ARP, QCI, GBR, MBR, and AMBR are short for allocation and retention priority, QoS class identifier, guaranteed bit rate,
maximum bit rate, and aggregate maximum bit rate, respectively.
A standardized QCI of a bearer includes the service priority, layer 2 (L2) packet delay budget (PDB), and
L2 packet error loss rate (PELR). For details, see section 6.1.7 in 3GPP TS 23.203 Release 10 issued in
March 2011.

eRAN
Huawei eNodeBs support extended QCIs. For details, see QoS Management Feature Parameter
Description.
3.1.2 Basic Functions

DL scheduling performs the following basic functions:
 Priority calculation
Based on the inputs, priority calculation determines the scheduling priorities of bearers and the UEs to
be scheduled. This satisfies the QoS requirements of UEs and maximizes system throughput. For
details, see section 3.4.1 "Obtaining DL Scheduling Resources"
 MCS selection
Based on the inputs, MCS selection determines an MCS for each UE selected. For details, see section
3.4.3 "Determining MCSs for DL Scheduling."
 Resource allocation
Based on the data volume and MCS, resource allocation determines the number of RBs to be
allocated to each UE as well as the position of each RB. For details, see section 3.4.4 "Determining
the Number of RBs for DL Scheduling."
3.1.3 Outputs
The scheduler determines the UEs to be scheduled, number of RBs to be allocated, position of each RB,
MCSs, TBSs, and multiple-input multiple-output (MIMO) mode.
3.1.4 Procedure for DL Scheduling in Each TTI

Figure 3-2 shows the overall procedure for DL scheduling in one TTI.

eRAN
Figure 3-2 Overall procedure for DL scheduling
In the procedure, the eNodeB takes the following actions:

1. Schedules common control information.
Common control information has the highest scheduling priority in the DL. For details, see 3.2
Scheduling Common Control Information.
2. Performs semi-persistent scheduling.
For details, see VoIP Feature Parameter Description.
3. Schedules UE-level control information.
For details, see 3.2 Scheduling Common Control Information.
4. Schedules HARQ retransmission data.
Retransmissions are scheduled based on the HARQ wait time. For details, see 3.3 Scheduling for DL
Retransmissions.
5. Schedules initial transmissions.
For details, see 3.4 DL Basic Scheduling for Initial Transmissions.
3.2 Scheduling Common Control Information

During scheduling in each subframe, control-plane messages are preferentially scheduled before
user-plane data. Control-plane information consists of common control information and dedicated control
information.

eRAN
 Common control information includes broadcast messages such as SIB1 and SIB2, and paging
messages. SIB is short for system information block.
 Dedicated control information includes random access (RA) response and the information carried on
signaling radio bearer (SRB) 0, SRB1, and SRB2.
Scheduling common control information uses QPSK and low coding rates for reliable transmission.
Resource allocation of type 2 is used to allocate resources to common control information. In resource
allocations of type 2, the allocations are classified into distributed virtual resource block (DVRB)
allocations and localized virtual resource block (LVRB) allocations. LVRB allocations are used by default.
The following describes DVRB allocations and LVRB allocations:
 DVRB allocation applies to the non-contiguous allocation of resource blocks and increases the
coverage of common control information. However, the system resources occupied by common
control information increases, resulting in a decrease in the UE throughput.
 LVRB allocation applies to the contiguous allocation of resource blocks and decreases the amount of
system resources occupied by common control information, which increases the UE throughput.
However, the coverage of common control information decreases.
3.3 Scheduling for DL Retransmissions

Huawei eNodeBs use adaptive asynchronous HARQ in the DL, corresponding to the basic feature
LBFD-002005 DL Asynchronous HARQ.
In adaptive asynchronous HARQ, a UE sends ACK or NACK i TTIs after the initial transmission, where i
is equal to 4 in frequency division (FDD) mode. If the UE sends an NACK, the eNodeB retransmits the
data k TTIs after receiving the NACK, where k is equal to 4 in FDD mode. The eNodeB adaptively
selects an MCS for HARQ retransmissions. HARQ retransmissions are scheduled after control-plane
messages. The scheduling priorities of different HARQ retransmissions are determined by the wait time.
A longer wait time indicates a higher scheduling priority. If all retransmissions have the same wait time, a
retransmission is randomly selected. If discontinuous reception (DRX) is enabled, the wait time is
determined by the DrxParaGroup.DrxReTxTimer parameter. If the wait time of an HARQ
retransmission exceeds a specified wait time, the HARQ retransmission is discarded. This ensures
effective retransmissions. For details about DRX, see DRX Feature Parameter Description.
During scheduling for HARQ retransmissions in each TTI, the eNodeB first schedules UEs based on the
HARQ priorities. The eNodeB then allocates retransmission resources to the UEs, and stops scheduling
when retransmissions for all UEs are complete or all resources are allocated.
The TBS in HARQ retransmissions is the same as the TBS in initial transmissions. Due to the use of soft
combining in HARQ, HARQ retransmissions can use a higher-order MCS than initial transmissions
based on CQI adjustment.
When ICIC is enabled, resources at the center bands are preferentially allocated to UEs in the center
and resources at the edge are preferentially allocated to UEs at the edge. If resources at the center or
edge band are insufficient, the resources of the entire band are used for allocation.
HARQ retransmissions cannot be performed for a UE in the following scenarios:
 The UE is in a measurement gap or enters a measurement gap when it sends an ACK or NACK.
 The UE enters sleep time in DRX and the HARQ operating status is discontinuous transmission
(DTX).
 The UE is not synchronized with the eNodeB or a radio link failure (RLF) occurs.
3.4 DL Basic Scheduling for Initial Transmissions

The feature related to DL basic scheduling is LBFD-002025 Basic Scheduling. Basic scheduling
performs three operations:

eRAN
 Acquires DL scheduling resources.

 Selects UEs to be scheduled.
 Determines MCSs to be used.
 Determines the number and positions of RBs to be allocated.
3.4.1 Obtaining DL Scheduling Resources

A basic function of DL scheduling is to obtain DL scheduling resources on the PDSCH. If power
allocation and inter-cell interference coordination (ICIC) are enabled in the DL, DL scheduling needs to
obtain resources based on power control and division between the edge band and center band. For
details about power control and ICIC, see Power Control Feature Parameter Description and ICIC
Feature Parameter Description, respectively.
Huawei eNodeBs support two DL resource allocation modes: frequency diversity scheduling and
frequency selective scheduling.
 Frequency diversity scheduling does not consider the differences in channel quality for UEs. The
eNodeB calculates the scheduling priorities based on the wideband CQIs reported by UEs. Based on
the priority calculation results, the eNodeB allocates DL resources to the UEs from the lower end to the
higher end of a frequency band, as shown in Figure 3-3.
 Frequency selective scheduling considers the differences in channel quality for UEs and brings
frequency selective scheduling gains. The eNodeB calculates the scheduling priorities based on
subband CQIs reported by UEs and schedules UEs based on the scheduling priorities of UEs in each
subband. In this mode, the UEs are scheduled to the subbands with the optimum channel quality. As
shown in Figure 3-4, resource block groups (RBGs) a and c are allocated to UE 1 and RBG b is
allocated to UE 2 because UE 1 and UE 2 have the highest scheduling priority in the scheduling queue
corresponding to the allocated RBGs.
Figure 3-3 Downlink resource allocation in frequency diversity scheduling

eRAN
Figure 3-4 Downlink resource allocation in frequency selective scheduling
Frequency selective scheduling requires accurate subband CQIs for scheduling priority calculation and
resource allocation. Frequency selective scheduling applies to slow-moving UEs because subband CQIs
reported by fast-moving UEs cannot reflect channel quality changes in a timely manner.
When the uplink load is high, the eNodeB prolongs the CQI reporting period and adjusts the CQI
reporting mode of UEs. For details, see section 3.5 "CSI Reporting." The prolonged CQI reporting period
and the changed CQI reporting mode decrease the gain of frequency selective scheduling.
Huawei eNodeBs use frequency selective scheduling by default. The scheduling method can be
specified by setting the CellAlgoSwitch.DISchSwitch parameter. In the current version, frequency
selective scheduling can take effect only when the PDCCH occupies three or more symbols.
3.4.2 Selecting UEs for DL Scheduling

Huawei eNodeBs support three basic scheduling policies: Max C/I, RR, and PF. An eNodeB can select
one of the three s policies. Figure 3-5 shows the relationships between the three policies.
Figure 3-5 Basic scheduling policies

eRAN
The Max C/I algorithm takes only the channel quality into account when allocating radio interface
resources and schedules services with the best channel quality at that moment. This algorithm
maximizes system throughput. However, it cannot ensure that UEs in the same cell are equally
scheduled because all UEs in a cell cannot experience the same channel conditions. If a UE is
constantly experiencing poor channel conditions, it cannot be scheduled. As a result, the user
experience is poor.
The RR algorithm allows UEs to take turns using shared resources. Compared with Max C/I, RR ensures
scheduling fairness between UEs in a cell. However, it cannot maximize the system throughput.
The PF algorithm is a compromise between Max C/I and RR. This algorithm takes the scheduling
fairness, channel quality, and number of transmitted bits into account. However, this algorithm does not
take the QoS requirements into account and therefore cannot ensure user experience.
The EPF algorithm is an enhancement to the PF algorithm. Compared with PF, EPF considers user
experience with services and ensures that QoS requirements are fulfilled. For details about the EPF
algorithm, see chapter 4 "DL Enhanced Scheduling."
An operator can select an appropriate scheduling policy by setting the CellDlschAlgo.DlschStrategy
parameter. For example, an operator can select Max C/I to achieve high system throughput for a peak
throughput test.
3.4.3 Determining MCSs for DL Scheduling

This section describes MCS selection for DL scheduling. The related features are as follows:
 LBFD-001006 AMC
The procedure for determining MCSs for DL scheduling is as follows:
1. If frequency diversity scheduling is used, the eNodeB selects an MCS based on the wideband CQI
reported by the UE. If frequency selective scheduling is used, the eNodeB selects an MCS based on
the subband CQIs reported by the UE. The eNodeB determines whether to adjust the CQI reported
by the UE as follows:
− Ifthe CQI adjustment algorithm is enabled, the eNodeB adjusts the CQI reported by the UE and
selects an MCS based on the adjusted CQI.
− If
the CQI adjustment algorithm is disabled, the eNodeB does not adjust the CQI reported by the UE
and selects an MCS based on the reported CQI.
The CellAlgoSwitch.CqiAdjAlgoSwitch specifies whether to enable the CQI adjustment algorithm.
2. The eNodeB maps the CQI reported by the UE to the Transport Block Size Index (ITBS), and then
maps the ITBS to the IMCS. IMCS is the MCS used for the UE to be scheduled. For details about the
mapping from ITBS to IMCS, see section 7.1.7 in 3GPP TS 36.213 Release 10 issued in March
2011.
A UE cannot report the CQI to the eNodeB immediately after being handed over to the target cell. In this
situation, to ensure a stable data transmission, the eNodeB temporarily uses the same MCS to transmit
data. Upon obtaining the CQI reported by the UE, the eNodeB dynamically selects an MCS to transmit
data.
In the DL, the broadcast channel, synchronization channel, and PDSCH share resources. If the resource
block allocated to a UE is occupied by broadcast signals or synchronization signals, the coding rate
increases when the TBS remains unchanged. An eNodeB selects another MCS to maximize the system
throughput based on how many resources are occupied.

eRAN
3.4.4 Determining the Number of RBs for DL Scheduling

The amount of data to be scheduled in a TTI determines the number of RBs to be scheduled for UEs.
Before determining the user data to be scheduled, a Huawei scheduler estimates the Radio Link Control
(RLC) overhead and MAC header overhead. This enables the scheduler to allocate scheduling
resources as precisely as possible, maximizing the resource utilization efficiency.
The scheduler then obtains the amount of data to be scheduled and the IMCS, and estimates the number
of RBs to schedule based on section 7.1.7 in 3GPP TS 36.213 Release 10 issued in March 2011. Based
on the remaining power of the cell, the scheduler determines the number of RBs to schedule for the UE.
For details about IMCS, see section 3.4.3 "Determining MCSs for DL Scheduling."
The scheduler selects the positions of the RBs to be scheduled based on the scheduling mode:
frequency diversity scheduling or frequency selective scheduling, For details about the scheduling
modes, see section 3.4.1 "Obtaining DL Scheduling Resources."
3.5 CSI Reporting

LBFD-002031 Support of aperiodic CQI reports is a basic scheduling feature.
Section 7.2 in 3GPP TS 36.213 Release 9 issued in September 2010 specifies multiple CSI reporting
modes listed in Table 3-1 and Table 3-2. In Table 3-1 and Table 3-2, the horizontal table header provides
the PMI feedback type and the vertical table header provides the PUSCH CQI feedback type.
Table 3-1 CQI and PMI feedback types for PUSCH reporting modes
No PMI Single PMI Multiple PMI
Wideband (wideband CQI) N/A N/A Mode 1-2
UE Selected (subband CQI) Mode 2-0 N/A Mode 2-2
Higher Layer-configured Mode 3-0 Mode 3-1 N/A
(subband CQI)
Table 3-2 CQI and PMI feedback types for PUCCH reporting modes
No PMI Single PMI
Wideband (wideband CQI) Mode 1-0 Mode 1-1
UE Selected (subband CQI) Mode 2-0 Mode 2-1
3GPP specifications stipulate that PUSCH reporting modes are aperiodic CSI reporting modes and
PUCCH reporting modes are periodic CSI reporting modes.
If a UE has no data to transmit, it transmits periodic CSI reports on the PUCCH. If a UE has data to
transmit, it transmits periodic CSI reports on the PUSCH. A UE transmits detailed aperiodic CSI reports
only on the PUSCH.
Compared with periodic CSI reporting, aperiodic CSI reporting contains more comprehensive
information, based on which the downlink scheduler performs frequency selective scheduling to obtain
the diversity gain. Each report in the aperiodic CSI reporting, however, contains more bits, and therefore
occupies more UL resources. Therefore, the CSI reporting mode is selected based on the following
principles:

eRAN
When few UEs in the cell are enabled with downlink frequency selective scheduling, aperiodic CSI
reporting is selected.
When many UEs in the cell are enabled with downlink frequency selective scheduling, periodic CSI
reporting is selected.
Table 3-3 provides a summary of the CSI reporting modes.
Table 3-3 CQI, PMI and RI reporting
Item Periodic Reporting Aperiodic Reporting
Physical channel PUCCH

PUSCH
for reporting (or PUSCH if data is also sent)
Trigger for reporting None Indication in UL scheduling grant
PMI feedback Single PMI Single PMI and multiple PMIs
1: wideband
1: wideband
2: UE selected subband (more
CQI feedback 2: UE selected best subband (less detailed; granular subband sizes)
detailed; coarse subband sizes)
3: higher-layer configured subband
Sent in separate subframes from
RI feedback Sent with CQI/PMI
CQI/PMI
The detailed selection method for the CSI reporting mode is as follows:
If frequency diversity scheduling is used in the DL, the eNodeB instructs UEs to periodically report CSIs.
The periodic CSI reporting mode is related to the MIMO mode used by the eNodeB. As shown in Figure
3-6, if open-loop MIMO is used, mode 1-0 is used by default. If closed-loop MIMO is used, mode 1-1 is
used by default.
The period of periodic CQI reporting is determined as follows:
 If adaptive CQI reporting is enabled, the eNodeB adjusts the CQI reporting period based on the
PUCCH load.
 If adaptive CQI reporting is disabled, the eNodeB uses the CQI reporting period specified by the
CqiAdaptiveCfg.UserCqiPeriodCfg parameter. The value range of this parameter is 2 ms, 5 ms, 10
ms, 20 ms, 32 ms, 40 ms, 64 ms, 80 ms, 128 ms, and 160 ms.
NOTE
Considering product implementation, when CqiAdaptiveCfg.UserCqiPeriodCfg is set to 32 ms, 64 ms, or 128 ms, the
CQI period is actually set to 20 ms, 40 ms, or 80 ms, respectively.
If frequency selective scheduling is used in the DL, the eNodeB instructs UEs to aperiodically as well as
periodically report CSIs. As shown in Figure 3-7, if open-loop MIMO is used, mode 3-0 is used. If
closed-loop MIMO is used, mode 3-1 is used. If the number of UEs to be scheduled using frequency
selective scheduling is greater than N (The value of N used by the internal algorithm is 10 and cannot be
changed), the eNodeB instructs UEs to periodically report subband CQIs to reduce the overhead of
uplink feedback. In this situation, if open-loop MIMO is used, mode 2-0 is used; if closed-loop MIMO is
used, mode 2-1 is used. The interval of aperiodical CQI reporting is related to the uplink load. The higher
the uplink load is, the longer the reporting interval is.

eRAN
Figure 3-6 CSI reporting mode in frequency diversity scheduling
Figure 3-7 CSI reporting mode in frequency selective scheduling

eRAN
Scheduling 4 DL Enhanced Scheduling
4 DL Enhanced Scheduling
As an enhancement to DL basic scheduling, DL enhanced scheduling adjusts which MCSs are
scheduled based on DL channel quality and HARQ feedback to increase the DL capacity and better
satisfy the QoS requirements of DL services.
4.1 DL CQI Adjustment

This section describes the downlink CQI adjustment algorithm, which is addressed in the optional
feature LOFD-00101501 CQI Adjustment.
CqiAdjAlgoSwitch under the CellAlgoSwitch.CqiAdjAlgoSwitch parameter determines whether the
downlink CQI adjustment algorithm is enabled.
If CqiAdjAlgoSwitch is set to Off, the downlink CQI adjustment algorithm is not used. The scheduler
selects an MCS based on the reported CQI. However, the UE-reported CQI cannot always reflect the
actual channel quality. Consider the following situations:
 The CQI reporting is delayed by N TTIs. (The value N is determined by the processing capability of the
eNodeB, transmission delay over the radio interface, and the CQI reporting period.) If the CQI
reporting delay is longer than the channel coherence time, the CQI reported by the UE is inconsistent
with the channel quality at the time of scheduling.
 The CQI reporting period is far greater than the scheduling period, which leads to a difference between
the CQI at the reporting time and the CQI at the scheduling time.
To handle these situations, the downlink CQI adjustment algorithm is introduced. If CqiAdjAlgoSwitch
is set to On, the downlink CQI adjustment algorithm is used. The eNodeB adjusts the UE-reported CQI
based on the ACK or NACK feedback from the UE; based on the adjusted CQI, the downlink scheduler
adjusts the MCS to reduce the initial block error rate (IBLER) to a specified target value and maximize
the system throughput.
An appropriate target IBLER value is crucial for efficient transmission and resource usage. If the target
IBLER value is set to a too low value, a low-order MCS will be selected for downlink data packets and
the transmission efficiency will be reduced. If the target IBLER value is set to a too high value, a
high-order MCS will be selected for downlink data packets. Consequently, the number of downlink
retransmissions increases and system resources are wasted. Based on analysis results, the optimum
target IBLER value is 10%, which is used as the default target IBLER value and cannot be changed.
The downlink CQI adjustment algorithm controls the MCS selection for downlink packets by adjusting the
CQI as follows:
 If the channel quality cannot meet the requirements of the MCS selected by the scheduler, the IBLER
increases. Then, the downlink CQI adjustment algorithm decreases the CQI value based on the NACK
feedback.
 If the channel quality meets the requirements of the MCS selected by the scheduler, the IBLER
decreases. Then, the downlink CQI adjustment algorithm increases the CQI value based on the ACK
feedback.
After proper MCS selection, the IBLER approximates to the target value and the system throughput
increases.
The step by which the CQI value is increased or decreased each time (referred to as the CQI adjustment
step in the following descriptions) is related to the setting of StepVarySwitch under the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter. Their relationships are as follows:
 StepVarySwitch is set to Off.
The CQI adjustment step is fixed.

eRAN
Scheduling 4 DL Enhanced Scheduling
 StepVarySwitch is set to On.

− The
UE has sparse downlink services. For example, the probability that the UE is scheduled in the
downlink within 100 ms is less than 10%.
The CQI adjustment step is constantly changing based on the difference between the current IBLER
value and the target IBLER value. A larger difference leads to a larger CQI adjustment step, thereby
speeding up the convergence to the target IBLER value.
− The UE has dense downlink services.
The CQI adjustment step is fixed.
4.2 DL Dynamic Scheduling

This section describes the optional feature LOFD-00101502 Dynamic Scheduling. A Huawei scheduler
uses the EPF scheduling algorithm to provide end-to-end QoS. This algorithm calculates the service
scheduling priorities and ensures service rates.
A Huawei scheduler can ensure the PELR and PDB as well as the service rate for GBR services. It can
ensure only the PELR for non-GBR services and uses a best effort policy in terms of the non-GBR
service rates. GBR services take precedence over non-GBR services if both services are running
simultaneously. For non-GBR services, there is a guarantee for the lowest service rate specified by the
StandardQci.DlMinGbr parameter. The following sections describe how to calculate the priorities of
GBR and non-GBR services.
4.2.1 Calculating the Priority of GBR Services

The priority of a GBR service is calculated by using the following formula:
Pr iority GBR
 f ( CQI )  f ( delay )
where
 f (CQI ) : indicates the channel quality.
 f (delay ) : indicates the PDB of the GBR service.
In addition, a GBR service can be scheduled multiple times. The scheduler checks the GBR service rate
at regular intervals and increases or decreases the number of times the GBR service is scheduled. This
ensures a stable GBR service rate.
4.2.2 Calculating the Priority of Non-GBR Services

The priority of a non-GBR service is calculated by using the following formula:
eff
Pr iority non  GBR
   QCI
r
where
 Eff: indicates the channel quality.
 r: indicates the historical number of transmitted bits for a UE.
  QCI : indicates the weight of the scheduling priority corresponding to a QCI. The
StandardQci.DlschPriorityFactor parameter specifies the weight factor used to calculate downlink
scheduling priorities. A larger value of this parameter indicates a higher scheduling priority. Weight
factors can be configured for both standardized QCIs and extended QCIs. Standardized QCIs are
defined in section 6.1.7 in 3GPP TS 23.203 Release 10 issued in March 2011. Extended QCIs are
based on standardized QCIs and enrich service levels.

eRAN
Scheduling 5 UL Basic Scheduling
5 UL Basic Scheduling
5.1 Introduction
In the LTE system, UL scheduling is performed at the MAC layer. UL scheduling allocates resources on
the physical uplink shared channel (PUSCH) to UEs and selects appropriate MCSs for the transmission
of user data.
Figure 5-1 shows the inputs, outputs, and basic functions of UL scheduling.
Figure 5-1 UL scheduling
SR: scheduling request BSR: Buffer Status Report

PHR: Power Headroom Report MU-MIMO: multiple user MIMO
UL basic scheduling involves the following features:

 LBFD-001006 AMC
 LBFD-002006 UL Synchronous HARQ
 LBFD-002025 Basic Scheduling
For details about the preceding features, see sections in this chapter.
UL enhanced scheduling involves the following features:
 LOFD-001006 UL 64QAM
 LOFD-00101502 Dynamic Scheduling
 LOFD-001048 TTI Bundling
For details about the preceding features, see 6 UL Enhanced Scheduling.

eRAN
5.1.1 Inputs
UE Capability
The input of UE capability for UL basic scheduling is the same as that described in 3.1.1 Inputs.
HARQ Feedback
The input of HARQ feedback for UL basic scheduling is the same as that described in 3.1.1 Inputs.
QoS Requirements
The input of QoS requirements for UL basic scheduling is the same as that described in 3.1.1 Inputs.
SINR
The UL scheduler schedules UEs and allocates resources to UEs based on the UL channel quality
indicated by the SINR, which is obtained by measuring sounding reference signals (SRSs) and
demodulation reference signals (DMRSs).
Power Headroom Report

A Power Headroom Report (PHR) shows the power headroom of a UE, which equals the difference
between the maximum TX power and the used TX power in the UL. The UE sends the PHR to the
eNodeB in either periodic mode or event-triggered mode.
The power headroom of a UE ranges from -23 dB to +40 dB. Based on the PHR, the UL scheduler
calculates the number of RBs required to maintain the maximum power spectrum density, which is
specified by the UL power control module. For details, see Power Control Feature Parameter
Description.
Buffer Status Report

A Buffer Status Report (BSR) shows the size of data contained in the UL buffer of a UE and is also sent
to the eNodeB.
Scheduling Request
A scheduling request (SR) is a 1-bit message sent from a UE to inform the eNodeB that the UE needs to
be allocated UL resources to transmit data.
5.1.2 Basic Functions

UL scheduling performs the following basic functions:
 Priority calculation
Based on the inputs, priority calculation determines the scheduling priorities of bearers and the UEs to
be scheduled. This satisfies the QoS requirements of UEs and maximizes system throughput. For
details, see section 5.3.1 "Obtaining UL Scheduling Resources."
 MCS selection
Based on the inputs, MCS selection is used to select an MCS for each UE. For details, see section
5.3.3 "Determining MCSs for UL Scheduling."
 Resource allocation
Based on the data volume and MCS, resource allocation determines the number of RBs to be
allocated to each UE as well as the position of each RB. For details, see section 5.3.4 "Determining
the Number of RBs for UL Scheduling."

eRAN
5.1.3 Outputs
The scheduler determines the UEs to be scheduled, number of RBs to be allocated, position of each RB,
MCSs, TBSs, and MIMO mode.
5.1.4 Procedure for UL Scheduling in Each TTI

Figure 5-2 shows the procedure for UL scheduling in each TTI.
Figure 5-2 Procedure for UL scheduling
In the procedure, the eNodeB takes the following actions:

1. Allocates resources for message 3 (Msg3).

eRAN
Scheduling for Msg3 is indicated in preambles and does not require messages on the physical
downlink control channel (PDCCH). For details, see 5.3 UL Dynamic Scheduling for Initial
Transmissions
2. Performs semi-persistent scheduling and schedule UEs in the TTI bundling state.
3. Schedule UEs in the TTI bundling state.
4. Allocates resources for synchronous HARQ.
For details, see 5.2 UL Dynamic Scheduling for Retransmissions.
5. Allocates resources for SRs.
For details, see 5.3 UL Dynamic Scheduling for Initial Transmissions.
6. Allocates resources for the control plane.
For details, see 5.3 UL Dynamic Scheduling for Initial Transmissions.
7. Schedules UEs with unsatisfied GBR.
For details, see 6.3 UL QoS Management.
8. Schedules UEs processing non-GBR services with bit rates lower than the UEs' AMBRs.
For details, see 6.3 UL QoS Management.
9. Schedules UEs that have been paired for MU-MIMO.
For details, see MIMO Feature Parameter Description.
10. Schedules UEs in UL CoMP mode.
For details, see UL CoMP Feature Parameter Description.
5.2 UL Dynamic Scheduling for Retransmissions

Synchronous HARQ is a basic feature for UL scheduling. After delivering an initial transmission indicator
to a UE, the eNodeB sends an ACK/NACK to the initial transmission within four TTIs and then
determines whether the UE needs to perform a retransmission.
Huawei eNodeB supports UL synchronous non-adaptive HARQ and synchronous adaptive HARQ. In
synchronous non-adaptive HARQ, the RB positions and MCS for retransmissions are identical to those
for the initial transmission. If the RB positions conflict with positions of PRACH and PUCCH resources,
the retransmission is suspended, affecting UL throughput. In synchronous adaptive HARQ, if data to be
retransmitted is allocated resources that conflict with other UL resources, the eNodeB adaptively adjusts
the number of RBs, their positions, and the MCS for retransmission. In this way, UL resources are
scheduled in a timely manner to reduce UL transmission latency and increase UL throughput. Huawei
eNodeB also supports automatic switching between the adaptive and non-adaptive modes. Operators
can specify the retransmission mode by the CellUlschAlgo.AdaptHarqSwitch parameter. The
automatic switching between the two modes is used by default.
Figure 5-3 shows the principle of automatic switching between UL synchronous non-adaptive HARQ and
synchronous adaptive HARQ.

eRAN
Figure 5-3 Automatic switching between the retransmission modes for UL dynamic scheduling
As defined in 3GPP TS 36.213, the MCS for UL synchronous adaptive HARQ remains unchanged for
initial transmissions and retransmissions. MCSs 29 to 31 are used, corresponding to different
redundancy versions.
5.3 UL Dynamic Scheduling for Initial Transmissions

UL dynamic scheduling for initial transmission performs three operations:
 Selects UEs for UL scheduling.
 Determines MCSs to be used.
 Determines the number of RBs to be allocated as well as their positions.
5.3.1 Obtaining UL Scheduling Resources

A basic function of UL scheduling is to obtain PUSCH resources. The PUSCH occupies the available UL
resources in addition to PUCCH and PRACH resources in the UL bandwidth. The PUCCH occupies RBs
at two ends of a cell bandwidth, and the number of RBs depends on the resources used to carry
information on the PUCCH. The information includes ACKs/NACKs to DL dynamic scheduling, DL CQIs,
the number of UEs in semi-persistent scheduling mode, and scheduling request indicators (SRIs). For
details about the PUCCH, see Physical Channel Resource Management Feature Parameter Description.
The PRACH periodically occupies 6 RBs at an interval specified by a related parameter.
According to section 5.3.3 in 3GPP TS23.211 Release 10 issued in March 2011, continuous uplink
resources are allocated and the number of allocated RBs is 2 k 1  3 k 2  5 k 3 , where k 1 , k 2 , and k 3 are
not minus integers.
NOTE
PUCCH: physical uplink control channel
PRACH: physical random access channel

eRAN
5.3.2 Selecting UEs for UL Scheduling

For UL scheduling, Huawei eNodeB also supports three basic scheduling policies identical to those for
DL scheduling. For details, see section 3.4.1 "Obtaining DL Scheduling Resources." The only difference
is the input for indicating the channel quality, which is the CQI for the DL and the SINR for the UL.
5.3.3 Determining MCSs for UL Scheduling

The process of determining MCSs for UL scheduling consists of three parts: SINR adjustment, initial
MCS selection, and MCS adjustment. Figure 5-4 shows the whole process, including the inputs and
outputs of the process.
Figure 5-4 Process of determining MCSs for UL scheduling
SINR Adjustment
SINR adjustment is specified by the CellAlgoSwitch.UlSchSwitch parameter. Due to the impact of
channel fading on signals of moving UEs, the SINR at the reporting time changes significantly, compared
with that at the scheduling time. Therefore, SINR adjustment is recommended. The eNodeB adjusts the
SINR based on ACKs/NACKs from UEs. In this way, SINR measurement errors can be corrected and
the measured IBLER value can be approximately equal to the target IBLER value, increasing system
throughput. The target IBLER value is specified by the CellUlschAlgo.SinrAdjustTargetIbler
parameter. The target IBLER value is 10% by default, but it may vary in different scenarios. Therefore,
set the target IBLER value based on site requirements.
Initial MCS Selection

An MCS is initially selected based on the measured SINR of the cell bandwidth and the eNodeB
modulation performance. To ensure the initial access performance, Huawei eNodeB uses a fixed
low-order MCS for message 3.
MCS Adjustment
After the initial MCS selection, the eNodeB can adjust the MCS based on the cell-specific SRS subframe
configuration and uplink control information on the PUSCH and also based on UE capabilities. The
cell-specific SRS subframes are used to transmit SRS signals, while the uplink control information is
transmitted using channel resources. The occupancy of resources on the PUSCH results in a higher
coding rate and accordingly a higher IBLER for initial data transmission. The MCS must be adjusted
accordingly to ensure that the scheduled data is correctly demodulated. UE capabilities must also be
considered because the highest-order MCS supported may vary for different UEs.
An MCS used for the uplink control information, such as ACKs, RIs, or CQIs, is selected based on the
result of the MCS used for data transmission minus an index offset. A higher index offset indicates a
higher transmission reliability, but more resources are used by the uplink control information. Generally,
the default index offsets are suitable and can be retained. However, if the uplink control information has a
high bit error rate (BER) in adverse radio conditions, higher index offsets can be specified by the

eRAN
PuschParam.DeltaOffsetAckIndex, PuschParam.DeltaOffsetRiIndex, and

PuschParam.DeltaOffsetCqiIndex parameters.
5.3.4 Determining the Number of RBs for UL Scheduling

The UL scheduler determines the RB resources required in the current TTI based on the buffer status
reported by UEs, token bucket status for QoS requirements, power headroom status, hardware
limitations, and maximum number of RBs supported by a single carrier.
The eNodeB determines the positions of RBs to be allocated based on factors such as the uplink SINR
measured by the eNodeB and system resource usage.

eRAN
Scheduling 6 UL Enhanced Scheduling
6 UL Enhanced Scheduling
As an enhancement to UL basic scheduling, UL enhanced scheduling selects a high-order MCS when
the UL channel quality is high to increase the UL capacity, transmits the same data block over
consecutive N subframes to increase the UL coverage and satisfy the QoS requirements for UL services.
6.1 UL 64QAM
UL 64QAM is an enhancement to UL modulation. This feature further increases UL spectral efficiency
and cell throughput and improves user experience when channel quality is favorable. For UEs
supporting UL 64QAM, they can transmit data using 64QAM when the SINR is satisfactory. UL 64QAM is
controlled by a license.
Only 3900 series eNodeBs support the feature LOFD-001006 UL 64QAM.
6.2 TTI Bundling

With TTI bundling, a transport block (TB) is transmitted within consecutive TTIs. These TTIs are bundled
and treated as one resource unit. When the UE channel quality is poor or the TX power is limited, this
feature can improve the edge coverage of the PUSCH, reduce the number of fragments on the radio link
control (RLC) layer, and reduce the signaling overhead. Currently, TTI bundling is not supported in a cell
with 1.4 MHz bandwidth and can only be used to improve the PUSCH edge coverage for VoIP services.
TTI bundling is controlled by the CellAlgoSwitch.UlSchSwitch parameter. After this switch is turned on,
the enabling and disabling of TTI bundling are triggered by RRC messages. This increases signaling
messages of the cell.
TTI bundling cannot be enabled together with the carrier aggregation or DRX.
A TTI bundle permanently consists of four TTIs. The same data is transmitted during the four TTIs. If
retransmission is required, synchronous adaptive HARQ and TTI bundling are used. In this case, the
retransmission interval is changed from eight TTIs of normal HARQ round trip time (RTT) to 16 TTIs of
bundle HARQ RTT, as shown in Figure 6-1.
Figure 6-1 TTI bundling
CRC: cyclic redundancy check
If TTI bundling is enabled, the eNodeB adaptively determines whether to use TTI bundling based on
channel conditions. The criterion is that UEs are at the cell edge and require TTI bundling to increase UL
edge coverage. The MCS and number of RBs used for TTI bundling vary according to the channel
quality and data volume to be transmitted. As defined in section 8.6.1 in 3GPP TS 36.213 Release 10
issued in March 2011, TTI bundling uses a maximum of three RBs and adopts QPSK and the MCS up to
10.

eRAN
6.3 UL QoS Management

A Huawei scheduler meets the end-to-end QoS requirements. Unlike DL QoS, UL QoS is ensured by
using related parameters sent from the eNodeB to UEs. The eNodeB can obtain accurate information
about the data amounts of downlink services and perform scheduling based on the data amounts and
service priorities. However, the eNodeB cannot obtain accurate information about the data amounts of
uplink services. Therefore, the eNodeB performs scheduling based on the scheduling priority, data
amounts, and service priorities of each UE. Because of this scheduling difference, the UL QoS
requirements are differentiated for different services of each UE.
The following describes the service rate control on the eNodeB and the parameter configuration for UEs:
 The eNodeB uses the UL scheduling algorithm to ensure that the total bit rate of non-GBR services of
a UE does not exceed the AMBR and that of GBR services does not exceed the MBR.
 For GBR services, the UL scheduler ensures the service rate.
 For non-GBR services, the UL scheduler uses a best-effort policy and only ensures the prioritized bit
rate (PBR) specified for each QCI.
According to 3GPP specifications, the PBR must be preferentially ensured on the UL logical channels
because of the following reasons:
 The PBR prevents the service rate from dropping to zero on low-priority logical channels due to
resource congestion.
 The PRB ensures that UEs on low-priority logical channels are scheduled even if resource congestion
occurs.
The value range of the PBR for logical channels is specified in section 6.2 in 3GPP TS 36.331 Release
10 issued in March 2011.
The PBR configuration principle for GBR services and non-GBR services is listed in Table 6-1.
Table 6-1 PBR configuration principle
Logical Channel Type PBR Configuration
DCCH (SRB 1 and SRB 2) Infinity
QCI 1 64 kbyte/s
QCI 2 to QCI 4 Configurable
QCI 5 8 kbyte/s
QCI 6 to QCI 9 Configurable
Extended QCI (QCI 10 to QCI 254) Configurable
The differentiation between services with different QCIs is achieved by setting parameters related to the
logical channel priorities. Logical channels represent the services on UEs. The parameters involved are
StandardQci.PrioritisedBitRate, StandardQci.LogicalChannelPriority, and
GlobalProcSwitch.LcgProfile. Their settings are delivered from the eNodeB to each UE in a radio
resource control (RRC) signaling message. Therefore, services with different QCIs can be prioritized as
required based on the logical channel priorities.
The logical channel priority can be set to a value in the range of 9 to 16, as specified by the
StandardQci.LogicalChannelPriority parameter. A larger value indicates a lower scheduling priority.
Logical channel priorities are configurable for QCIs 6 to 9 and extended QCIs. Because all extended

eRAN
QCIs correspond to non-GBR services, the logical channel priorities for extended QCIs cannot be higher
than the logical channel priorities for any GBR services. The UE can report the total amount of buffered
data for multiple services, but not for each individual service. This reduces the system resource
consumption. These services must be mapped to the same logical channel. The eNodeB supports four
logical channel groups.
The GlobalProcSwitch.LcgProfile parameter, which specifies the logical channel group profile, can be
set to LCG_PROFILE_0 or LCG_PROFILE_1. If the parameter is set to LCG_PROFILE_0, only one
logical channel group is assigned to non-GBR services. If the parameter is set to LCG_PROFILE_1, two
logical channel groups are assigned to non-GBR services: one to high-priority non-GBR services and the
other to low-priority non-GBR services.
6.4 Preallocation Scheduling

Based on UL loads, the eNodeB can perform preallocation to reserve resources for UEs requiring short
delays. The preallocation function is controlled by a switch under the CellAlgoSwitch.UlSchSwitch
parameter. The total resources for preallocation are specified by the
CellUlschAlgo.PreAllocationBandwidthRatio parameter. This parameter indicates the maximum
proportion of the total RBs available for preallocated UEs in a TTI to the system bandwidth. The amount
of data that can be preallocated to a UE in a preallocation queue is specified by the
CellUlschAlgo.PreAllocationSize parameter.
If the preallocation function is enabled, and PUSCH resources are still available after the UEs with
unsatisfied GBR and UEs with normal uplink services are scheduled, a UE that meets the following
conditions is placed in the preallocation queue:
 It is not scheduled within the current TTI.
 It is not in the DRX mode.
For details about DRX, see DRX Feature Parameter Description.
 It meets the requirements for minimum interval between preallocations.
The minimum interval between preallocations is specified by the
CellUlschAlgo.PreAllocationMinPeriod parameter. If the interval is 1, UEs can be preallocated in
each TTI. If the interval is 2, UEs can be preallocated once every two TTIs.
 It has a preallocation weight greater than 0.
The preallocation weight is specified by the StandardQci.PreAllocationWeight parameter, which is
QCI-specific. The preallocation weight of a UE is determined by the preallocation weight of the
services with the highest-priority QCI.
The resource preallocation priorities of UEs in the preallocation queue are determined by the number of
preallocations and the preallocation weight. A UE with a smaller number of preallocations and a larger
preallocation weight has a higher priority. If UEs have the same priority and preallocation weight, the
UEs are randomly selected for preallocation. Preallocation is unavailable for UEs undergoing
semi-persistent scheduling.

eRAN
Scheduling 7 Cooperation with Other Features
7 Cooperation with Other Features

7.1 Scheduling in RAN Sharing Mode
If the ENodeBSharingMode.ENodeBSharingMode parameter is set to
COMMON_CARRIER_SHARE(RAN Sharing with Common Carrier Mode) and the
CellAlgoSwitch.RanShareModeSwitch parameter is set to ON(On), scheduling in radio access
network (RAN) sharing mode applies. In this case, the eNodeB identifies different operators' UEs by their
public land mobile network (PLMN) IDs.
In such a scheduling procedure, the proportion of resources for each operator is determined by the
CellOp.OpDlRbUsedRatio and CellOp.OpUlRbUsedRatio parameters for the DL and UL, respectively.
For different operators, the scheduling priorities depend on the ratio of the actual RB usage to the target
RB usage.
NOTE
The actual RB usage of an operator is the ratio of the number of RBs used by the operator in a period to the total number
of RBs on the PDSCH or PUSCH for DL or UL transmission, respectively.
For UEs of the same operator, their scheduling priorities are handled in the same way as in normal UL
and DL scheduling procedures.
Keep in mind the following rules for UL scheduling:
 During resource preallocation, eNodeBs do not differentiate between operators of UEs.
 Scheduling for UE pairing can be performed only on UEs of the same operator in multi-user MIMO
scenarios.
 Only 3900 series eNodeBs support the feature LOFD-001036 RAN Sharing with Common Carrier.

eRAN
Scheduling 8 Related Features and Their Impacts on the Network
8 Related Features and Their Impacts on the Network

This chapter describes the relationships between scheduling features and other features and the impact
of the scheduling features on the network.
8.1 Scheduling Feature Selection Principles

The following are the overall principles for selecting scheduling features:
Features 1 to 5 are mandatory for an eNodeB to run properly. They are compatible with all other eNodeB
features.
1. LBFD-001005 Modulation: DL/UL QPSK, DL/UL 16QAM, DL 64QAM
2. LBFD-001006 AMC
3. LBFD-002005 DL Asynchronous HARQ
4. LBFD-002006 UL Synchronous HARQ
5. LBFD-002031 Support of aperiodic CQI reports
Features 6 and 7 contain functions from which operators can select one. They are also compatible with
all other eNodeB features.
6. LBFD-002025 Basic Scheduling
7. LOFD-001015 Enhanced Scheduling
Features 8 and 9 have specific network requirements.
8. LOFD-001006 UL 64QAM
9. LOFD-001048 TTI Bundling
8.2 DL Scheduling
This section describes the relationships between DL scheduling features and other features and the
impact of the DL scheduling features on the network.
8.2.1 Required Features

None.
8.2.2 Mutually Exclusive Features

LBFD-002025 Basic Scheduling is exclusive to LOFD-00101502 Dynamic Scheduling.
8.2.3 Affected Features

DL scheduling does not affect other features.
8.2.4 Impact on the Network

Features 1, 2, 3 and 5 are used by default. They are essential to eNodeBs. They increase system
throughput based on CSI from UEs. In addition, they improve coverage performance by reliably
transmitting broadcast information, system information, and signaling messages during procedures such
as handovers.
Feature 6 is a basic feature. Operators determine which algorithm in feature 6 to use.

eRAN
Scheduling 8 Related Features and Their Impacts on the Network
Feature 7 is recommended for commercial networks to improve DL performance in cells and service
quality. Feature 7 introduces CQI adjustment and QoS management. It increases system throughput,
improves user experience, and helps meet QoS requirements.
8.3 UL Scheduling
This section describes the relationships between UL scheduling features and other features and the
impact of the UL scheduling features on the network.
8.3.1 Required Features

LOFD-001048 TTI Bundling is required only for VoIP services.
8.3.2 Mutually Exclusive Features

 LBFD-002025 Basic Scheduling is exclusive to LOFD-00101502 Dynamic Scheduling.
 LOFD-001048 TTI Bundling is exclusive to LBFD-002017 DRX.
 LOFD-001048 TTI Bundling is exclusive to LOFD-001105 Dynamic DRX.
 LOFD-001048 TTI Bundling is exclusive to LOFD-001097 Carrier Aggregation Introduction Package
(Two Component Carriers).
8.3.3 Affected Features

UL scheduling does not affect other features.
8.3.4 Impact on the Network

Features 1, 2, and 4 are used by default. They are essential to eNodeBs. They increase system
throughput based on CSI from UEs.
Features 8 and 9 are enhancements of UL scheduling. Operators optionally use them. These features
are fit for scenarios where UL coverage is limited or UL transmit power is insufficient. Feature 8 further
increases UL throughput. Feature 9 improves UL edge coverage for VoIP services. The enabling and
disabling of this feature, however, increase signaling messages of the cell because they are triggered by
RRC messages.

eRAN
Scheduling 9 Engineering Guidelines for DL Basic Scheduling
9 Engineering Guidelines for DL Basic Scheduling

This chapter provides engineering guidelines for DL basic scheduling. The following features are not
described in this chapter because they are enabled by default and no configurable parameter is
involved:
 LBFD-001006 AMC
 LBFD-002005 DL Asynchronous HARQ
 LBFD-002031 Support of aperiodic CQI reports
9.1 When to Use Scheduling

9.1.1 LBFD-002025 Basic Scheduling
Scheduling Policies
The basic scheduling policies are Max C/I, PF, and RR. The following are suggestions for selecting
scheduling policies:
 To achieve the maximum system capacity, use the Max C/I policy.
This policy prioritizes UEs with better channel quality. The Max C/I policy achieves high spectral
efficiency but does not ensure QoS or scheduling fairness for UEs.
 To achieve a balance between system capacity and scheduling fairness, use the PF policy.
This policy achieves a balance between Max C/I and RR, but does not meet QoS requirements of
UEs.
 To achieve scheduling fairness, use the RR policy.
This policy schedules each UE the same number of times, but results in low system capacity.
Adaptive CQI Reporting

Adaptive CQI reporting is recommended for use on commercial networks.
Adaptive CQI reporting adjusts the CQI reporting period based on the PUCCH load. The CQI reporting
period of UEs increases with the PUCCH load. When the number of UEs is small, a short CQI reporting
period is used to maximize the UE throughput. When the number of UEs is large, a long CQI reporting
period is used to maximize the number of UEs in a cell. Adaptive CQI reporting achieves a tradeoff
between the number of UEs in a cell and cell capacity.
9.2 Information to Be Collected

None
9.3 Network Planning

None
9.4 Deploying Basic Scheduling Policies

9.4.1 Deployment Requirements
Basic scheduling policies have no requirements for operating environments, transmission networking, or
licenses.

eRAN
9.4.2 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.
Generic Data
The following table describes the parameters that must be set in the CellDlschAlgo managed object
(MO) to set the DL scheduling policy for each cell.
Parameter Parameter ID Source Setting Description

Name
Local cell CellDlschAlgo.Loc Network plan Set this parameter based on the network plan.
ID alCellId (negotiation This parameter specifies the local identity of a
not required) cell. Ensure that this parameter has been set in
the related Cell MO.
Downlink CellDlschAlgo.Dls Network plan This parameter specifies the DL scheduling
scheduling chStrategy (negotiation policy. There are four policies: Max C/I, RR, PF,
Strategy not required) and EPF. Select Max C/I, RR, or PF as a basic
scheduling policy.
Scenario-specific Data
The following table describes the parameters that must be set in the CQIADAPTIVECFG MO to set
adaptive CQI reporting for each cell.
Parameter Parameter ID Data Source Setting Notes

Name
CQI period CQIADAPTIVECFG.CqiP Network plan This parameter specifies whether to
adaptive eriodAdaptive (negotiation enable adaptive CQI reporting. Adaptive
switch not required) CQI reporting is recommended for
normally operating networks.
User CQI CQIADAPTIVECFG.User Network plan This parameter specifies the fixed CQI
period config CqiPeriodCfg (negotiation reporting period when adaptive CQI
not required) reporting is disabled.
9.4.3 Precautions
None

eRAN
9.4.4 Initial Configuration

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 9.4.2 "Data Preparation." For details,
see the procedure for configuring a single eNodeB on the CME GUI described in eNodeB Initial
Configuration Guide.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in Table 9-1, and save the parameter settings as a
user-defined template.
The parameters are the same as those described in section 9.4.2 "Data Preparation."
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-1 Parameters related to basic scheduling policies
MO Parameter Group Name Parameter
CELLDLSCHALGO CellDlschAlgo LocalCellID, Downlink scheduling Strategy
CQIADAPTIVECFG CQIADAPTIVECFG CQI period adaptive switch, User CQI period
config
Configuring a Single eNodeB Using MML Commands

1. Run the MOD CELLDLSCHALGO command to set the DL scheduling policy for each cell.
2. Run the MOD CQIADAPTIVECFG command to enable adaptive CQI reporting.
9.4.5 Activation Observation

This section describes the procedures for verifying the activation of DL and UL basic scheduling policies.
The following examples show test results for commercial UEs in cells with bandwidths of 20 MHz.
Verifying Max C/I for DL Scheduling

To verify whether Max C/I has been activated for DL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell. Perform DL packet injection on the default bearer of each UE to
ensure that the DL cell throughput reaches its maximum.
Step 2 On the M2000 client, start channel quality monitoring, MCS-based count monitoring, and
throughput monitoring on each UE. The following are methods for starting these tasks:

eRAN
− Tostart channel quality monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring > Quality
of Channel Monitoring.
− Tostart MCS-based count monitoring, choose Monitoring > Signaling Trace > Signaling
Trace Management. Then in the navigation tree, choose User Performance Monitoring >
MCS Count Monitoring.
− To
start throughput monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring >
Throughput Monitoring.
Step 3 Adjust the positions of the two UEs in the cell so that UE 1 experiences good DL channel quality
and UE 2 experiences poor DL channel quality.
Figure 9-1 and Figure 9-2 show examples of channel quality monitoring results for UE 1 and UE 2,
respectively. In these examples, the CQI for UE 1 is 25, and the CQI for UE 2 is 8.
Figure 9-1 Example of channel quality monitoring results for UE 1
Step 4 Check the MCS-based count monitoring results for the number of DL RBs allocated to each UE.
Then check the throughput monitoring results for the DL throughput of each UE.
If UE 1 occupies a majority of the total DL cell throughput and has been allocated more RBs than UE 2,
Max C/I has been activated successfully. Figure 9-3 through Figure 9-6 show examples of the monitoring
results.

eRAN
Figure 9-3 Example of MCS-based count monitoring results for UE 1
Figure 9-5 Example of throughput monitoring results for UE 1

eRAN
----End
Verifying RR for DL Scheduling

To verify whether RR has been activated for DL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell in the cell center. Perform a DL service on the default bearer of
each UE.
Step 2 On the M2000 client, start channel quality monitoring and MCS-based count monitoring on each
UE. The following are methods for starting these tasks:
Step 3 Check the channel quality monitoring results for the DL channel quality of each UE.
Figure 9-7 and Figure 9-8 show examples of the monitoring results. In these examples, the CQI for both
UEs is 25.

eRAN
Step 4 Check the MCS-based count monitoring results for the number of times each UE is scheduled in
the DL.
If the results are approximately the same for both UEs, RR has been activated successfully. Figure 9-9
and Figure 9-10 show examples of the monitoring results.
----End

eRAN
Verifying PF for DL Scheduling

To verify whether PF has been activated for DL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell. Perform a DL service on the default bearer of each UE.
Step 3 Adjust the positions of the two UEs in the cell so that UE 1 experiences good DL channel quality
and UE 2 experiences poor DL channel quality. For example, the CQI for UE 1 is 25, and the CQI
for UE 2 is 8.
If the results are approximately the same for both UEs, PF has been activated successfully. Figure 9-11

eRAN
----End
Verifying Adaptive CQI Reporting

Verify whether adaptive CQI reporting has taken effect as follows:
Step 1 Set the CqiPeriodAdaptive parameter and the UserCqiPeriodCfg parameter to OFF and ms10,
respectively.
Step 2 Check the value of the IE cqi-pmi-ConfigIndex in the RRC_ONN_RECFG message over the Uu
interface.
If the value of the IE is 0xa(10), the CQI reporting period is 10 ms and adaptive CQI reporting has taken
effect.
For details about CQI reporting period, see table 7.2.2-1A in section 7.2.2 of 3GPP TS 36.213.
Figure 9-13 Example of the UE-level CQI reporting period configuration
----End

eRAN
9.5 Performance Optimization

None
9.6 Troubleshooting
None.

eRAN 10 Engineering Guidelines for DL Enhanced
Scheduling Scheduling
10 Engineering Guidelines for DL Enhanced Scheduling

This chapter provides engineering guidelines for DL enhanced scheduling.

10.1.1 LOFD-00101501 CQI Adjustment
CQI adjustment is recommended for use on commercial networks. It is an enhanced feature for DL
scheduling. This feature uses a closed-loop MCS adjustment mechanism to correct UE-reported CQIs
and combat channel condition changes during the time between CQI reporting and scheduling. In
addition, CQI adjustment enables the DL IBLER to converge on the target value and therefore increasing
DL throughput.
10.1.2 LOFD-00101502 Dynamic Scheduling

Scheduling Policies
Enhanced scheduling uses EPF as the scheduling policy. This policy takes scheduling fairness, cell
capacity, and QoS satisfaction into consideration.
Enhanced scheduling is recommended for use on commercial networks.
Resource Allocation
Huawei eNodeBs support two DL resource allocation modes: frequency diversity scheduling and
frequency selective scheduling. Huawei eNodeBs use frequency selective scheduling by default.
Frequency selective scheduling considers the differences in channel quality for UEs and brings gains.
Frequency selective scheduling is not recommended in the following situations:
 UEs are moving at a high speed.
 The UL load is high.
 Frequency selective scheduling does not take effect if the PDCCH occupies less than three symbols.

None

None
10.4 Deploying CQI Adjustment

Operating Environment
N/A
Transmission Networking
N/A

License
The operator has purchased and activated the license for the feature listed in Table 10-1. For details
about how to activate a license, see License Management Feature Parameter Description.
Table 10-1 License information for CQI adjustment
Feature License Control Item
LOFD-00101501 CQI Adjustment Enhanced Scheduling (per RRC Connected User)

Generic Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to activate CQI
adjustment for each cell.

Name
Local cell ID CellAlgoSwitch.Lo Network plan Set this parameter based on the network plan.
calCellId (negotiation This parameter specifies the local identity of a
not required) cell. Ensure that this parameter has been set
in the related Cell MO.
CQI adjust CellAlgoSwitch.Cq Network plan CqiAdjAlgoSwitch under this parameter
algorithm iAdjAlgoSwitch (negotiation specifies whether to activate CQI adjustment.
switch not required) CQI adjustment is recommended for normally
operating networks.
StepVarySwitch under this parameter
specifies whether to use the
variable-step-based adjustment algorithm. The
use of this algorithm can speed up the
convergence to the target IBLER value.
This switch takes effect only if
CqiAdjAlgoSwitch is set to On.
N/A

10.4.3 Precautions
None

Configure a single eNodeB using the CME GUI based on the collected data described in section 10.4.2
"Data Preparation." For details, see the procedure for configuring a single eNodeB on the CME GUI
described in eNodeB Initial Configuration Guide.

----End
Table 10-2 Parameters related to CQI adjustment
CELLALGOSWITCH CellAlgoSwitch LocalCellID, CQI adjust algorithm switch

Run the MOD CELLALGOSWITCH command to activate CQI adjustment.

To verify whether CQI adjustment has been activated, perform the following steps:
Step 1 Enable a UE to access a cell in the cell center.
Step 2 On the M2000 client, start channel quality monitoring and BLER monitoring on the UE. The
following are methods for starting these tasks:
− To
start BLER monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring > BLER
Monitoring.

Step 3 Perform DL packet injection on the UE so that the UE is scheduled about 1000 times per second
in the DL. At the same time, move the UE gradually to the cell edge.
Step 4 Check the channel quality monitoring results for the DL channel quality, and check the BLER
monitoring results for the DL IBLER.
----End
Figure 10-1 and Figure 10-2 show examples of the monitoring results. In these examples, the CQI is
approximately 18, and the value of Downlink IBLER(Permillage) fluctuates approximately 100, which
means that the DL IBLER converges on the default value 10%. The results indicate that CQI adjustment
has been activated.
Figure 10-1 Example of channel quality monitoring results
Figure 10-2 Example of BLER monitoring results
10.5 Deploying the Dynamic Scheduling

N/A

N/A
License
Table 10-3 License information for CQI adjustment
LOFD-00101502 Dynamic Scheduling Enhanced Scheduling (per RRC Connected User)

Generic Data
The following table describes the parameters that must be set in the CellDlschAlgo MO to set the DL
scheduling policy for each cell.

Name
Local cell CellDlschAlgo.L Network plan Set this parameter based on the network plan.
ID ocalCellId (negotiation This parameter specifies the local identity of a
Downlink CellDlschAlgo.Dl Network plan This parameter specifies the DL scheduling
scheduling schStrategy (negotiation policy. There are four policies: Max C/I, RR, PF,
Strategy not required) and EPF. Select EPF as the enhanced
scheduling policy.
The following table describes the parameters that must be set in the StandardQci MO to configure
service differentiation used in the enhanced scheduling policy for each cell.


Name
Downlink StandardQci.D Network plan If this parameter is set to a large value, the
MinGBR lMinGbr (negotiation Min_GBR (minimum guaranteed bit rate) of
not required) high-priority non-GBR services can be
guaranteed but the Min_GBR of low-priority
non-GBR services may fail to be guaranteed
when resources are insufficient.
If this parameter is set to a small value, there
might be an impact on the response time of
non-GBR services.
In a normally operating network, the default value
is recommended.
Pre-allocation StandardQci.P Network plan This parameter affects the preallocation
weight reAllocationW (negotiation probability for services with the QCI and therefore
eight not required) affects the service delay. The delay has a
negative correlation with the preallocation weight.
is recommended.
Prioritised bit StandardQci.P Network plan If this parameter is set to PBR_0_KBps(0KB/s),
rate rioritisedBitRa (negotiation there is a risk that services with the QCI will never
te not required) be scheduled. If this parameter is set to
PBR_INFINITY(Infinity) and the traffic volume of
services with the QCI is high, there is a risk that
services with QCIs indicating lower priorities than
this QCI will never be scheduled.
Logical StandardQci.L Network plan Services with relatively high priorities are
channel ogicalChannel (negotiation preferentially scheduled.
priority Priority not required) In a normally operating network, the default value
is recommended.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to configure
the logical channel group used in the enhanced scheduling policy for each cell.

Name
LCG Profile GlobalProcSwi Network plan If this parameter is set to LCG_PROFILE_1,
tch.LcgProfile (negotiation non-GBR services are classified into high- and
not required) low-priority non-GBR services. QoS requirements
of high-priority non-GBR services are better
fulfilled, but there is a risk of failure to meet QoS
requirements of low-priority non-GBR services.
For detailed setting descriptions, see section 6.3
"UL QoS Management."

10.5.3 Precautions
DL frequency selective scheduling does not support online configuration. When the status of the switch
for DL frequency selective scheduling is changed, enable UEs to access the network again to obtain
reliable test results.

"Data Preparation." For details, see the procedure for configuring a single eNodeB on the CME GUI

----End
Table 10-4 Parameters related to the enhanced scheduling policy
CELLDLSCHALGO CellDlschAlgo LocalCellID, Downlink scheduling
Strategy

Run the MOD CELLDLSCHALGO command to set the DL scheduling policy for each cell.

Verifying EPF for DL Scheduling
To verify whether EPF has been activated for DL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell in the cell center.

Step 3 Check the channel quality monitoring results for the DL channel quality of each UE.
Figure 10-3 and Figure 10-4 show examples of the monitoring results. In these examples, the CQI for
both UEs is 25.
Step 4 Run the LST STANDARDQCI command to query the DL scheduling weight factors for QCIs 6
and 9.
Step 5 Perform a DL service with QCI 6 on UE 1 and a DL service with QCI 9 on UE 2.
If the ratio of the number for UE 1 to the number for UE 2 is approximately equal to the ratio of the weight
factor for QCI 6 to the weight factor for QCI 9, EPF has been activated successfully. Figure 10-5 and
Figure 10-6 show examples of the monitoring results.

----End

None
10.7 Troubleshooting
None.

eRAN
Scheduling 11 Engineering Guidelines for UL Basic Scheduling
11 Engineering Guidelines for UL Basic Scheduling

This chapter provides engineering guidelines for UL basic scheduling. The following features are not
described in this chapter because they are enabled by default and no configurable parameter is
involved:
 LBFD-001006 AMC
 LBFD-002006 UL Synchronous HARQ

11.1.1 LBFD-002025 Basic Scheduling
For details, see 9.1.1 LBFD-002025 Basic Scheduling.

None

None
11.4 Deploying Basic Scheduling Policies

Basic scheduling policies have no requirements for operating environments, transmission networking, or
licenses.

Generic Data
The following table describes the parameters that must be set in the CellUlschAlgo MO to set the UL

eRAN

Name
Local cell CellUlschAlgo.LocalCellId Network plan Set this parameter based on the
ID (negotiation not network plan. This parameter specifies
required) the local identity of a cell. Ensure that
this parameter has been set in the
related Cell MO.
Uplink CellUlschAlgo.UlschStrat Network plan This parameter specifies the UL
Scheduling egy (negotiation not scheduling policy. There are four
Strategy required) policies: Max C/I, RR, PF, and EPF.
Select Max C/I, RR, or PF as a basic
scheduling policy.
NA
11.4.3 Precautions
None

Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 11.4.2 "Data Preparation." For details,
see the procedure for configuring a single eNodeB on the CME GUI described in eNodeB Initial
Configuration Guide.

----End
Table 11-1 Parameters related to basic scheduling policies
CELLULSCHALGO CellUlschAlgo LocalCellID, Uplink Scheduling Strategy

eRAN

Run the MOD CELLULSCHALGO command to set the UL scheduling policy for each cell.

This section describes the procedures for verifying the activation of DL and UL basic scheduling policies.
The following examples show test results for commercial UEs in cells with bandwidths of 20 MHz.
Verifying Max C/I for UL Scheduling

To verify whether Max C/I has been activated for UL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell. Perform UL packet injection on the default bearer of each UE to
ensure that the UL cell throughput reaches its maximum.
Step 2 On the M2000 client, start channel quality monitoring, MCS-based count monitoring, and
throughput monitoring on each UE. The following are methods for starting these tasks:
− To
Step 3 Adjust the positions of the two UEs in the cell so that UE 1 experiences good UL channel quality
and UE 2 experiences poor UL channel quality.
Figure 11-1 and Figure 11-2 show examples of channel quality monitoring results for UE 1 and UE 2,
respectively. In these examples, the SINR for UE 1 is approximately 21 dB, and the SINR for UE 2 is
approximately 10 dB.

eRAN
Step 4 Check the MCS-based count monitoring results for the number of UL RBs allocated to each UE,
and check the throughput monitoring results for the UL throughput of each UE.
If UE 1 occupies a majority of the total UL cell throughput and has been allocated more RBs than UE 2,
Max C/I has been activated successfully. Figure 11-3 through Figure 11-6 show examples of the
monitoring results.

eRAN
----End

eRAN
Verifying RR for UL Scheduling

To verify whether RR has been activated for UL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell in the cell center. Perform a UL service on the default bearer of
each UE.
Step 3 Check the channel quality monitoring results for the UL channel quality of each UE.
Figure 11-7 and Figure 11-8 show examples of the monitoring results. In these examples, the SINR for
both UEs is approximately 21 dB.
Step 4 Check the MCS-based count monitoring results for the number of times each UE is scheduled in
the UL.

eRAN
If the results are approximately the same for both UEs, RR has been activated successfully. Figure 11-9
----End
Verifying PF for UL Scheduling

To verify whether PF has been activated for UL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell. Perform a UL service on the default bearer of each UE.

eRAN
Step 3 Adjust the positions of the two UEs in the cell so that UE 1 experiences good UL channel quality
and UE 2 experiences poor UL channel quality. As an example, the SINR for UE 1 is
approximately 21 dB, and the SINR for UE 2 is approximately 10 dB.
Step 4 Check the MCS-based count monitoring results for the number of UL RBs allocated to each UE.
If the results are approximately the same for both UEs, PF has been activated successfully. Figure 11-11
----End

None
None.

eRAN 12 Engineering Guidelines for UL Enhanced
12 Engineering Guidelines for UL Enhanced Scheduling

This chapter provides engineering guidelines for UL enhanced scheduling.

12.1.1 LOFD-001006 UL 64QAM
UL 64QAM is recommended if radio conditions are favorable and UEs support UL 64QAM. This feature
increases UL throughput and improves user experience.
12.1.2 LOFD-00101502 Dynamic Scheduling

Enhanced Scheduling policy
For details, see 10.1.2 LOFD-00101502 Dynamic Scheduling.
SINR Adjustment
SINR adjustment is recommended for use on commercial networks. It is similar to CQI adjustment for DL
scheduling. The SINR adjustment feature corrects UL SINR measurement errors and combats channel
condition changes during the time between SINR measurement and scheduling. SINR adjustment
enables the UL IBLER to converge on the target value, therefore increasing UL throughput.
UL Preallocation
UL preallocation is recommended for use on delay-sensitive networks or networks with only a few UL
services during the early stages of network construction. This feature reduces the service transmission
delay but increases signaling overheads and UL resource consumption.
12.1.3 LOFD-001048 TTI Bundling

TTI bundling is recommended if UL coverage is poor and UE power is insufficient. This feature enhances
PUSCH coverage for especially indoor VoIP services.

None

None
12.4 Deploying UL 64QAM

Requirements for the Operating Environment
N/A
Requirements for Transmission Networking

N/A

Requirements for Licenses

Operators must purchase and activate the following license.
Feature License Control Item Name

LOFD-001006 UL 64QAM UL 64QAM

Generic Data
N/A
The following table describes the parameters that must be set in the PUSCHCfg MO to activate UL
64QAM for each cell.

Name
Local cell ID PUSCHCfg.Local Network plan Set this parameter based on the network plan.
CellId (negotiation This parameter specifies the local identity of a
Qam64 PUSCHCfg.Qam6 Network plan This parameter specifies whether to activate UL
enabled 4Enabled (negotiation 64QAM in the cell.
not required)
12.4.3 Precautions
None

Data Preparation. For details, see the procedure for configuring a single eNodeB on the CME GUI


The parameters are the same as those described in section 12.4.2 Data Preparation.
----End
Table 12-1 Parameters related to UL 64QAM
CELLALGOSWITCH PUSCHCfg LocalCellID, Qam64 enabled

Run the MOD PUSCHCFG command to activate UL 64QAM.
Example:
MOD PUSCHCFG: LOCALCELLID=0, QAM64ENABLED=BOOLEAN_TRUE;

To verify whether UL 64QAM has been activated, perform the following steps:
Step 1 On the M2000 client, choose Monitoring > Signaling Trace > Signaling Trace Management,
and in the navigation tree choose Application Layer > Uu Interface Trace to start Uu interface
tracing.
Step 2 Run the MOD PUSCHCFG command to activate 64QAM in a cell. Run the DEA CELL command
to deactivate the cell, and then run the ACT CELL command to activate the cell.
Step 3 In the Uu interface tracing result, check the information element (IE) enable64QAM in the
RRC_SYS_INFO message in system information block type 2 (SIB2):
radioResourceConfigCommon > pusch-ConfigCommon > pusch-ConfigBasic > enable64QAM.
If the value of enable64QAM is TRUE, the cell supports UL 64QAM.
Step 4 Enable a UE of category 5 to access the cell in the cell center. Perform a UL File Transfer
Protocol (FTP) service on the UE.
Step 5 On the M2000 client, start channel quality monitoring and throughput monitoring on the UE. The
− To
start channel quality monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring > Quality of
Channel Monitoring.

− To
Step 6 Check the channel quality monitoring results for the UL SINR, and check the throughput
monitoring results for the UL throughput.
Figure 12-1 and Figure 12-2 show examples of the monitoring results. In these examples, the UL SINR is
approximately 23.5 dB, and the UL throughput is approximately 57 Mbit/s.
Figure 12-2 Example of throughput monitoring results
Step 7 Run the MOD PUSCHCFG command to deactivate 64QAM in the cell. Run the DEA CELL
command to deactivate the cell, and then run the ACT CELL command to activate the cell.
Step 8 In the Uu interface tracing result, check the IE enable64QAM in the RRC_SYS_INFO message
in SIB2: radioResourceConfigCommon > pusch-ConfigCommon > pusch-ConfigBasic >
enable64QAM.
If the value of enable64QAM is FALSE, the cell does not support UL 64QAM.
Step 9 Enable the UE to access the cell at the same place in the cell center. Perform UL packet injection
on the UE to ensure that the UL cell throughput reaches its maximum.
Step 10 Repeat Step 5..
Step 11 Check the throughput monitoring results for the UL throughput.

Figure 12-3 shows an example of the monitoring results. In the example, the UL throughput is
approximately 47 Mbit/s.
Figure 12-3 Example of throughput monitoring results
The UE has higher throughput when the cell supports UL 64QAM. This indicates that UL 64QAM has
been activated successfully.
----End
12.5 Deploying the Dynamic Scheduling

N/A
N/A
License
Table 12-2 License information for UL Dynamic Scheduling
LOFD-00101502 Dynamic Scheduling Enhanced Scheduling (per RRC Connected User)


Generic Data
The following table describes the parameters that must be set in the CellUlschAlgo MO to set the UL

Name
Local cell CellUlschAlgo.Lo Network plan Set this parameter based on the network plan.
ID calCellId (negotiation This parameter specifies the local identity of a
Uplink CellUlschAlgo.Ul Network plan This parameter specifies the UL scheduling
Scheduling schStrategy (negotiation policy. There are four policies: Max C/I, RR, PF,
Strategy not required) and EPF. Select EPF as the enhanced
scheduling policy.
The following table describes the parameters that must be set in the StandardQci MO to configure
service differentiation used in the enhanced scheduling policy for each cell.

Name
Downlink StandardQci.D Network plan If this parameter is set to a large value, the
MinGBR lMinGbr (negotiation Min_GBR (minimum guaranteed bit rate) of
not required) high-priority non-GBR services can be
guaranteed but the Min_GBR of low-priority
non-GBR services may fail to be guaranteed
when resources are insufficient.
If this parameter is set to a small value, there
might be an impact on the response time of
non-GBR services.
is recommended.
Pre-allocation StandardQci.P Network plan This parameter affects the preallocation
weight reAllocationW (negotiation probability for services with the QCI and therefore
eight not required) affects the service delay. The delay has a
negative correlation with the preallocation weight.
is recommended.


Name
Prioritised bit StandardQci.P Network plan If this parameter is set to PBR_0_KBps(0KB/s),
rate rioritisedBitRa (negotiation there is a risk that services with the QCI will never
te not required) be scheduled. If this parameter is set to
PBR_INFINITY(Infinity) and the traffic volume of
services with the QCI is high, there is a risk that
services with QCIs indicating lower priorities than
this QCI will never be scheduled.
Logical StandardQci.L Network plan Services with relatively high priorities are
channel ogicalChannel (negotiation preferentially scheduled.
priority Priority not required) In a normally operating network, the default value
is recommended.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to configure
the logical channel group used in the enhanced scheduling policy for each cell.

Name
LCG Profile GlobalProcSwi Network plan If this parameter is set to LCG_PROFILE_1,
tch.LcgProfile (negotiation non-GBR services are classified into high- and
not required) low-priority non-GBR services. QoS requirements
of high-priority non-GBR services are better
fulfilled, but there is a risk of failure to meet QoS
requirements of low-priority non-GBR services.
For detailed setting descriptions, see section 6.3
"UL QoS Management."
The following table describes the parameters that must be set in the CellAlgoSwitch MO to activate
SINR adjustment for each cell.

Name
Local cell ID CellAlgoSwitch.L Network plan Set this parameter based on the network plan.
ocalCellId (negotiation not This parameter specifies the local identity of a
required) cell. Ensure that this parameter has been set in
Uplink CellAlgoSwitch.U Network plan SinrAdjustSwitch(SinrAdjustSwitch) under
schedule lSchSwitch (negotiation not this parameter specifies whether to activate
switch required) SINR adjustment.
SINR adjustment is recommended for normally
operating networks.
PuschDtxSwitch(PuschDtxSwitch) under
this parameter specifies whether the eNodeB
uses the PUSCH DTX detection result during
UL scheduling. If this switch is turned on, the


Name
eNodeB determines whether to perform an
adaptive retransmission during UL scheduling
based on the PUSCH DTX detection result.
The eNodeB also adjusts the CCE aggregation
level of the PDCCH carrying DCI format 0
based on the same result.
The following table describes the parameters that must be set in the CellUlschAlgo MO to set the target
IBLER value for SINR adjustment in each cell.

Name
Local cell ID CellUlschAlgo.L Network plan Set this parameter based on the network plan.
SINR target CellUlschAlgo.Si Network plan This parameter specifies the target IBLER value
IBLER nrAdjustTargetI (negotiation not used in the SINR adjustment algorithm. A larger
adjustment bler required) value of this parameter results in greater SINR
adjustments and higher-order MCSs selected.
The recommended value is 10.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to activate UL
preallocation for each cell.

Name
Local cell ID CellAlgoSwitch. Network plan Set this parameter based on the network plan.
LocalCellId (negotiation not This parameter specifies the local identity of a
Uplink CellAlgoSwitch. Network plan PreAllocationSwitch(PreAllocationSwitch)
schedule UlSchSwitch (negotiation not under this parameter specifies whether to
switch required) activate preallocation.
SmartPreAllocationSwitch(SmartPreAllocatio
nSwitch) under this parameter specifies whether
to enable UL smart preallocation when the
PreAllocationSwitch(PreAllocationSwitch)
check box is selected.
In a normally operating network, select the
PreAllocationSwitch(PreAllocationSwitch)
check box and clear the
SmartPreAllocationSwitch(SmartPreAllocatio
nSwitch) check box.

The following table describes the parameters that must be set in the CellUlschAlgo MO to use UL
preallocation for each cell.

Name
Local cell ID CellUlschAlgo.L Network plan Set this parameter based on the network plan.
System CellUlschAlgo.P Network plan This parameter specifies the ratio of the
Bandwidth reAllocationBan (negotiation not maximum bandwidth for preallocated UEs to the
Ratio Used dwidthRatio required) system bandwidth .
By If the cell bandwidth is 1.4 MHz, the
Pre-schedul recommended value of this parameter is 50%. If
e user per the cell bandwidth is not 1.4 MHz, the
TTI recommended value of this parameter is 25%.
minimal CellUlschAlgo.P Network plan This parameter specifies the minimum interval
period of reAllocationMin (negotiation not between two preallocations to one UE.
pre-allocatio Period required) The recommended value is 5.
n
data size of CellUlschAlgo.P Network plan This parameter specifies the amount of data
pre-allocatio reAllocationSize (negotiation not preallocated to each UE.
n required) The recommended value is 80.
12.5.3 Precautions
None



----End
Table 12-3 Parameters related to the enhanced scheduling policy
CELLULSCHALGO CELLULSCHALGO LocalCellID/ Uplink Scheduling Strategy/
SINR target IBLER adjustment(0.01) /
System Bandwidth Ratio Used By
Pre-schedule user per TTI/ minimal
period of pre-allocation/ data size of
pre-allocation/Smart pre-allocation
duration
CELLALGOSWITCH CELLALGOSWITCH LocalCellID/ Uplink schedule switch
STANARDQCI STANARDQCI PreAllocationWeight

 Setting the UL scheduling policy
Run the MOD CELLULSCHALGO command to set the UL scheduling policy.
Example:
MOD CELLULSCHALGO:LOCALCELLID=0,ULSCHSTRATEGY=ULSCH_STRATEGY_EPF;
 Activating SINR adjustment

Run the MOD CELLALGOSWITCH command to activate SINR adjustment.
Example:
MOD CELLALGOSWITCH:LOCALCELLID=0, ULSCHSWITCH=SinrAdjustSwitch-1;
 Activating preallocation
Run the MOD CELLALGOSWITCH command to activate UL preallocation.
Example:
MOD CELLALGOSWITCH:LOCALCELLID=0, ULSCHSWITCH=PreAllocationSwitch-1;

Verifying EPF for UL Scheduling
To verify whether EPF has been activated for UL scheduling, perform the following steps:
Step 1 Enable two UEs to access a cell in the cell center.

Step 3 Check the channel quality monitoring results for the UL channel quality of each UE.
Figure 12-4 and Figure 12-5 show examples of the monitoring results. In these examples, the SINR for
both UEs is approximately 21 dB.
Step 4 Run the LST STANDARDQCI command to query the UL scheduling weight factors for QCIs 6
and 9.
Step 5 Perform a UL service with QCI 6 on UE 1 and a UL service with QCI 9 on UE 2.
Step 6 Check the MCS-based count monitoring results for the number of UL RBs allocated to each UE.
If the ratio of the number for UE 1 to the number for UE 2 is approximately equal to the ratio of the weight
factor for QCI 6 to the weight factor for QCI 9, EPF has been activated successfully. Figure 12-6 and
Figure 12-7 show examples of the monitoring results.

----End
To verify whether SINR adjustment has been activated, perform the following steps:
Step 1 Enable a UE to access a cell in the cell center.
Step 2 On the M2000 client, start channel quality monitoring and BLER monitoring on the UE. The
− To
start channel quality monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring > Quality of
Channel Monitoring.
− To
start BLER monitoring, choose Monitoring > Signaling Trace > Signaling Trace
Management. Then in the navigation tree, choose User Performance Monitoring > BLER
Monitoring.
Step 3 Perform UL packet injection on the UE so that the UE is scheduled about 1000 times per second
in the UL. At the same time, move the UE gradually to the cell edge.
Step 4 Check the channel quality monitoring results for the UL channel quality, and check the BLER
monitoring results for the UL IBLER.

Figure 12-8 and Figure 12-9 show examples of the monitoring results. In these examples, the SINR is
approximately 6.5 dB, and the value of Uplink IBLER(Permillage) fluctuates approximately 100, which
means that the UL IBLER converges on the default value 10%. The results indicate that SINR
adjustment has been activated.
Figure 12-9 Example of BLER monitoring results
----End
To verify whether preallocation has been activated, perform the following steps:
Step 1 Enable a UE to access a cell in the cell center. Do not perform UL services on the UE.
Step 2 On the M2000 client, start channel quality monitoring and MCS-based count monitoring on the
Step 3 Check the channel quality monitoring results for the UL channel quality, and check the
MCS-based count monitoring results for the number of times the UE is scheduled in the UL.

Figure 12-10 and Figure 12-11 show examples of the monitoring results. In these examples, the SINR is
approximately 20.5 dB, and the UE is scheduled 200 times per second in the UL. The number of
scheduling times is consistent with the default preallocation period of 5 ms. The results indicate that
preallocation has been activated.
Figure 12-11 Example of MCS-based count monitoring results
----End
12.6 Deploying TTI Bundling

Requirements for the Operating Environment
N/A
Requirements for Transmission Networking

N/A
Requirements for Licenses

Operators must purchase and activate the following license.

Feature License Control Item Name

LOFD-001048 TTI Bundling TTI Bundling

Generic Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to activate TTI
bundling for each cell.

Name
Local cell ID CellAlgoSwitc Network plan Set this parameter based on the network plan.
h.LocalCellId (negotiation not This parameter specifies the local identity of a
required) cell. Ensure that this parameter has been set
in the related Cell MO.
Uplink CellAlgoSwitc Network plan TtiBundlingSwitch(TtiBundlingSwitch)
schedule h.UlSchSwitch (negotiation not under this parameter specifies whether to
switch required) activate TTI bundling. The following are setting
suggestions:
 In a normally operating network, clear the
TtiBundlingSwitch(TtiBundlingSwitch)
check box.
 In activation scenarios described in section
12.1.3 LOFD-001048 TTI Bundling, select
the
TtiBundlingSwitch(TtiBundlingSwitch)
check box.
N/A
12.6.3 Precautions
None



----End
Table 12-4 Parameters related to TTI bundling
CELLALGOSWITCH CellAlgoSwitch LocalCellID, Uplink schedule switch

Run the MOD CELLALGOSWITCH command to activate TTI bundling.

To verify whether TTI bundling has been activated, perform the following steps:
Step 1 On the M2000 client, start Uu interface tracing. In this step, select a test cell and set Report
Type to Message Report.
Step 2 Enable a UE to access a cell, and perform a UL FTP service on the UE.
Step 3 Move the UE to the cell edge until RRC_CONN_RECFG and RRC_CONN_RECFG_CMP
messages are traced on the Uu interface.
Step 4 Check the IE ttiBundling in the RRC_CONN_RECFG message: mac-MainConfig >
ul-SCH-Config > ttiBundling.
If the value of ttiBundling is TRUE, the UL FTP service enters the TTI bundling state.
Step 5 Move the UE from the cell edge to the cell center. Check the IE ttiBundling in the
RRC_CONN_RECFG message: mac-MainConfig > ul-SCH-Config > ttiBundling.
If the value of ttiBundling is FALSE, the UL FTP service exits the TTI bundling state.

----End

None
None.

eRAN
Scheduling 13 Parameters
13 Parameters
Table 13-1 Parameter description
MO Parameter ID MML Feature ID Feature Description
Command Name
CellUlschAlg AdaptHarqSwitch MOD LBFD-0020 UL Meaning:Indicates the switch

o CELLULSCHAL 06 / Synchron that is used to control whether
GO TDLBFD-00 ous to enable or disable UL
2006 HARQ adaptive HARQ. If this switch is
LST set to
CELLULSCHAL ADAPTIVE_HARQ_SW_OFF,
GO UL data is retransmitted by
non-adaptive synchronous
HARQ. If this switch is set to
ADAPTIVE_HARQ_SW_ON,
UL data is retransmitted by
adaptive synchronous HARQ. If
this switch is set to
ADAPTIVE_HARQ_SW_SEMI
ON, adaptive HARQ is triggered
when a UL grant is delivered to
an HARQ process that is
previously suspended due to
reasons such as resource
collision, activation of a
measurement gap, and PDCCH
congestion.
GUI Value
Range:ADAPTIVE_HARQ_SW
_ON(On),
ADAPTIVE_HARQ_SW_OFF(
Off),
ADAPTIVE_HARQ_SW_SEMI_
ON(SemiOn)
Unit:None
Actual Value
Range:ADAPTIVE_HARQ_SW
_ON,
ADAPTIVE_HARQ_SW_OFF,
ADAPTIVE_HARQ_SW_SEMI_
ON
Default
Value:ADAPTIVE_HARQ_SW_
SEMI_ON(SemiOn)
CellAlgoSwit CqiAdjAlgoSwitch MOD LOFD-0010 UL 2x2 Meaning:CqiAdjAlgoSwitch:

ch CELLALGOSWI 02 / MU-MIM Indicates the switch used to
TCH TDLOFD-00 O control whether to allow the
1002 eNodeB to adjust the
LST CQI UE-reported CQI on the basis of

eRAN

Command Name
CELLALGOSWI LOFD-0010 Adjustme Initial Block Error Rate (IBLER).
TCH 1501 / nt
TDLOFD-00 If this switch is turned on, the
101501 Dynamic CQI adjustment algorithm is
Schedulin enabled. In the case, the
LOFD-0010 g eNodeB would adjust the
1502 / UE-reported CQI based on the
TDLOFD-00 IBLER.
101502
If this switch is turned off, the
CQI adjustment algorithm is
disabled. In this case, the
eNodeB would not adjust the
UE-reported CQI based on the
IBLER.
StepVarySwitch: Indicates the
switch used to enable or disable
the variable-step-based
adjustment algorithm.
If this switch is turned on, the
variable-step-based adjustment
algorithm is enabled to
accelerate the convergence of
IBLER. In this case, rapid
adjustment at large steps is
applied if there is a relatively
large difference between the
measured IBLER and target
IBLER; fine-tuning at small
steps is applied if the measured
IBLER approaches the target
IBLER.
If this switch is set to Off, the
adjustment is performed at a
fixed step.
GUI Value
Range:CqiAdjAlgoSwitch,
StepVarySwitch
Unit:None
Actual Value
Range:CqiAdjAlgoSwitch,
StepVarySwitch
Default
Value:CqiAdjAlgoSwitch:On,
StepVarySwitch:Off
CqiAdaptive CqiPeriodAdaptiv MOD LBFD-0020 Basic Meaning:Indicates whether to

CQIADAPTIVE 25 / Schedulin enable or disable CQI reporting

eRAN

Command Name
Cfg e CFG TDLBFD-00 g period adaptation. This
2025 parameter is valid only for FDD
LST cells.
CQIADAPTIVE
CFG GUI Value Range:OFF(Off),
ON(On)
Unit:None
Actual Value Range:OFF, ON
Default Value:ON(On)
PuschParam DeltaOffsetAckIn MOD None None Meaning:Indicates the index

dex PUSCHPARAM mapped to the MCS offset for
acknowledgments (ACKs)
LST transmitted with data on
PUSCHPARAM PUSCH. The protocol does not
recommend the value 15. If this
parameter is set to 15, If this
value is used, the UE
performance may deteriorate.
For details, see 3GPP TS
36.213.
GUI Value Range:0~15
Unit:None
Actual Value Range:0~15
Default Value:9
PuschParam DeltaOffsetCqiInd MOD None None Meaning:Indicates the index

ex PUSCHPARAM mapped to the MCS offset for
channel quality indicators
LST (CQIs) transmitted with data on
PUSCHPARAM PUSCH.
Unit:None
Default Value:12
PuschParam DeltaOffsetRiInde MOD None None Meaning:Indicates the index

x PUSCHPARAM mapped to the MCS offset for
rank indications (RIs)
LST transmitted with data on
PUSCHPARAM PUSCH. The protocol does not
recommend the values 13, 14,
and 15. If this parameter is set
to 13, 14, or 15, If this value is

eRAN

Command Name
used, the UE performance may
deteriorate. For details, see
3GPP TS 36.213.
Unit:None
Default Value:5
StandardQci DlMinGbr MOD LBFD-0020 Basic Meaning:Indicates the downlink

STANDARDQCI 25 / Schedulin minimum guaranteed bit rate of
TDLBFD-00 g the non-GBR service.
LST 2025
STANDARDQCI Enhanced GUI Value
LOFD-0010 Schedulin Range:MinGbrRate_0_KB(0KB/
15 / g s), MinGbrRate_1_KB(1KB/s),
TDLOFD-00 MinGbrRate_2_KB(2KB/s),
1015 Basic Qos MinGbrRate_4KB(4KB/s),
Managem MinGbrRate_8_KB(8KB/s),
LBFD-0030 ent MinGbrRate_16_KB(16KB/s),
02 / MinGbrRate_32_KB(32KB/s),
TDLBFD-00 Dynamic MinGbrRate_64_KB(64KB/s),
3002 Schedulin
g MinGbrRate_128_KB(128KB/s)
LOFD-0010 ,
1502 / Enhanced MinGbrRate_256_KB(256KB/s)
TDLOFD-00 Transmis ,
101502 sion QoS MinGbrRate_512_KB(512KB/s)
Managem
LOFD-0030 ent Unit:KB/s
11 / Actual Value
TDLOFD-00 Range:MinGbrRate_0_KB,
3011 MinGbrRate_1_KB,
MinGbrRate_2_KB,
MinGbrRate_4KB,
MinGbrRate_8_KB,
MinGbrRate_16_KB,
MinGbrRate_32_KB,
MinGbrRate_64_KB,
MinGbrRate_128_KB,
MinGbrRate_256_KB,
MinGbrRate_512_KB
Default
Value:MinGbrRate_1_KB(1KB/s
)
StandardQci DlschPriorityFact MOD LOFD-0010 Enhanced Meaning:Indicates the weight

or STANDARDQCI 15 / Schedulin factor used in the calculation of
TDLOFD-00 g connection priorities during
LST 1015 downlink scheduling.
Dynamic

eRAN

Command Name
STANDARDQCI LOFD-0010 Schedulin GUI Value Range:1~1000
1502 / g
TDLOFD-00 Unit:0.001
101502 Actual Value Range:0.001~1,
step:0.001
Default Value:700
CellDlschAlg DlschStrategy MOD LBFD-0020 Basic Meaning:Indicates the switch of

o CELLDLSCHAL 25 / Schedulin the DL scheduling policy.
GO TDLBFD-00 g According to the Max C/I
2025 scheduling policy, the UE with
LST Enhanced good-quality channels are
CELLDLSCHAL LOFD-0010 Schedulin scheduled and hence the
GO 15 / g spectral efficiency is very high.
TDLOFD-00 The QoS and fairness among
1015 users, however, cannot be
ensured. The Max C/I
scheduling policy can be used
to verify the maximum capacity
of the system. The RR
scheduling policy is the fairest
scheduling policy. When RR is
adopted, the system capacity is
the smallest. Therefore, RR is
used only to verify the upper
bound of the scheduling
fairness in the system. In terms
of the scheduling effect, the PF
scheduling policy is between
the previous two policies.
Therefore, PF can be used to
verify the capacity, coverage,
and fairness of the system. The
EPF scheduling policy supports
the features such as user QoS,
system capacity, and channel
frequency selection. The basic
scheduling policy is mainly used
for the performance test
purpose. During common
operation, the EPF scheduling
policy is recommended.
GUI Value
Range:DLSCH_PRI_TYPE_EP
F(EPF),
DLSCH_PRI_TYPE_PF(PF),
DLSCH_PRI_TYPE_MAX_CI(
MAX C/I),
DLSCH_PRI_TYPE_RR(RR)

eRAN

Command Name
Unit:None
Actual Value
Range:DLSCH_PRI_TYPE_EP
F, DLSCH_PRI_TYPE_PF,
DLSCH_PRI_TYPE_MAX_CI,
DLSCH_PRI_TYPE_RR
Default
Value:DLSCH_PRI_TYPE_EPF
(EPF)
CellAlgoSwit DlSchSwitch MOD LBFD-0020 Basic Meaning:Indicates the switches

ch CELLALGOSWI 25 / Schedulin related to DL scheduling in the
TCH TDLBFD-00 g cell.
2025
LST Enhanced FreqSelSwitch: Indicates
CELLALGOSWI LOFD-0010 Schedulin whether to enable or disable
TCH 15 / g frequency selection and
TDLOFD-00 scheduling. If this switch is
1015 VoIP turned on, data is transmitted
Semi-pers on the frequency band with
LOFD-0010 istent good-quality channels.
16 / Schedulin
TDLOFD-00 g ServiceDiffSwitch: Indicates
1016 whether to enable or disable
Symbol service differentiation. If this
LOFD-0010 Power switch is turned on, service
70 / Saving differentiation is available. If this
TDLOFD-00 switch is turned off, service
1070 differentiation is unavailable.
SpsSchSwitch: Indicates
whether to enable or disable
semi-persistent scheduling
during talk spurts of VoIP
services. If this switch is turned
on, semi-persistent scheduling
is applied. If this switch is
turned off, dynamic scheduling
is applied.
MBSFNShutDownSwitch:
Indicates whether to enable or
disable Multimedia Broadcast
Single Frequency Network
(MBSFN) subframe shutdown.
If this switch is turned on,
MBSFN subframe shutdown is
available. If this switch is turned
off, MBSFN subframe shutdown
is unavailable. This switch is
valid only when symbol-based
power amplifier (PA) shutdown

eRAN

Command Name
is enabled. If the MBSFN
subframe shutdown switch is
valid, the switch for the mapping
from SIBs to SI messages
becomes invalid. If the MBSFN
subframe shutdown switch is
invalid, the switch for the
mapping from SIBs to SI
messages becomes valid.
MBSFN subframe shutdown
applies only to single-mode
eNodeBs.
GUI Value
Range:FreqSelSwitch(FreqSel
Switch),
ServiceDiffSwitch(ServiceDiffS
witch),
SpsSchSwitch(SpsSchSwitch),
MBSFNShutDownSwitch(MBS
FNShutDownSwitch)
Unit:None
Actual Value
Range:FreqSelSwitch,
ServiceDiffSwitch,
SpsSchSwitch,
MBSFNShutDownSwitch
Default
Value:FreqSelSwitch:Off,
ServiceDiffSwitch:Off,
SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off
DrxParaGrou DrxReTxTimer ADD LBFD-0020 DRX Meaning:Indicates the length of

p DRXPARAGRO 17 / the DRX Retransmission Timer.
UP TDLBFD-00 DL
2017 Asynchro GUI Value Range:sf1(1
MOD nous subframe), sf2(2 subframes),
DRXPARAGRO LBFD-0020 HARQ sf4(4 subframes), sf6(6
UP 05 / subframes), sf8(8 subframes),
TDLBFD-00 sf16(16 subframes), sf24(24
LST 2005 subframes), sf33(33 subframes)
DRXPARAGRO
UP Unit:subframe
Actual Value Range:sf1, sf2,
sf4, sf6, sf8, sf16, sf24, sf33
Default Value:sf8(8 subframes)
ENodeBShar ENodeBSharingMMOD LOFD-0010 RAN Meaning:Indicates the eNodeB

eRAN

Command Name
ingMode ode ENODEBSHARI 36 / Sharing sharing mode, which can be
NGMODE TDLOFD-00 with independent Operator Mode,
1036 Common Shared Frequency Sharing
LST Carrier Mode, or Separate Frequency
ENODEBSHARI LOFD-0010 Sharing Mode.
NGMODE 37 / RAN
TDLOFD-00 Sharing GUI Value
1037 with Range:INDEPENDENT(Indepe
Dedicated ndent Operator Mode),
Carrier SHARED_FREQ(Shared
Frequency Sharing Mode),
SEPARATED_FREQ(Separate
Frequency Sharing Mode)
Unit:None
Actual Value
Range:INDEPENDENT,
SHARED_FREQ,
SEPARATED_FREQ
Default
Value:INDEPENDENT(Indepen
dent Operator Mode)
GlobalProcS LcgProfile MOD LBFD-0020 Basic Meaning:Indicates whether to

witch GLOBALPROC 25 / Schedulin set a logical channel group
SWITCH TDLBFD-00 g profile.
2025
LST Enhanced Currently, two logical channel
GLOBALPROC LOFD-0010 Schedulin group profiles are available:
SWITCH 15 / g LCG_PROFILE_0 and
TDLOFD-00 LCG_PROFILE_1. If
1015 LCG_PROFILE_0 is used, only
one logical channel group is
assigned to non-GBR services.
If LCG_PROFILE_1 is used,
two logical channel groups are
assigned to non-GBR services:
one to high-priority non-GBR
services and the other to
low-priority non-GBR services.
GUI Value
Range:LCG_PROFILE_0,
LCG_PROFILE_1
Unit:None
Actual Value
Range:LCG_PROFILE_0,
LCG_PROFILE_1
Default

eRAN

Command Name
Value:LCG_PROFILE_0
CellUlschAlg LocalCellId LST None None Meaning:Indicates the local ID

o CELLULSCHAL of the cell. It uniquely identifies
GO a cell within a BS.
MOD GUI Value Range:0~17
CELLULSCHAL
GO Unit:None
Default Value:None
CellAlgoSwit LocalCellId LST None None Meaning:Indicates the local ID

ch CELLALGOSWI of the cell. It uniquely identifies
TCH a cell within a BS.
CELLALGOSWI
TCH Unit:None
Default Value:None
PUSCHCfg LocalCellId LST None None Meaning:Indicates the local ID

PUSCHCFG of the cell. It uniquely identifies
a cell within a BS.
MOD
PUSCHCFG GUI Value Range:0~17
Unit:None
Default Value:None
CellDlschAlg LocalCellId LST None None Meaning:Indicates the local ID

o CELLDLSCHAL of the cell. It uniquely identifies
GO a cell within a BS.
CELLDLSCHAL
GO Unit:None
Default Value:None
StandardQci LogicalChannelPr MOD LBFD-0020 Basic Meaning:Indicates the priority of

iority STANDARDQCI 25 / Schedulin the logical channel. The UE
TDLBFD-00 g scheduler guarantees
LST 2025 prioritized bit rates of logical
STANDARDQCI Enhanced channels in an ascending order
LOFD-0010 Schedulin of logical channel priorities.

eRAN

Command Name
15 / g Resources are allocated in an
TDLOFD-00 ascending order of logical
1015 channel priorities after the
prioritized bit rates of all
services are guaranteed. For
details, see 3GPP TS 36.321.
Unit:None
Default Value:11
CellOp OpDlRbUsedRati ADD CELLOP LBFD-0010 3GPP R8 Meaning:Indicates the

o 01 / Specificati percentage of RBs occupied by
MOD CELLOP TDLBFD-00 ons the operator on the PDSCH
LST CELLOP 1001 when RAN sharing is enabled at
Broadcast the eNodeB and the cell-level
LBFD-0020 of system switch of RAN sharing is turned
09 / informatio on. When the data volume is
TDLBFD-00 n sufficiently large, the
2009 percentage of RBs occupied by
Cell
LBFD-0020 Selection each operator will reach the
1803 / and preset value. Modifications on
TDLBFD-00 Reselecti this parameter affect operators'
201803 on percentages of RBs.
LOFD-0010 RAN GUI Value Range:1~100

36 / Sharing Unit:%
TDLOFD-00 with
1036 Common Actual Value Range:1~100
Carrier
Default Value:16
CellOp OpUlRbUsedRati ADD CELLOP LBFD-0010 3GPP R8 Meaning:Indicates the

o 01 / Specificati percentage of RBs occupied by
MOD CELLOP TDLBFD-00 ons the operator on the PUSCH
LST CELLOP 1001 when RAN sharing is enabled at
Broadcast the eNodeB and the cell-level
LBFD-0020 of system switch of RAN sharing is turned
09 / informatio on. When the data volume is
TDLBFD-00 n sufficiently large, the
2009 percentage of RBs occupied by
Cell
LBFD-0020 Selection each operator will reach the
1803 / and preset value. Modifications on
TDLBFD-00 Reselecti this parameter affect operators'
201803 on percentages of RBs.
LOFD-0010 RAN GUI Value Range:1~100

36 / Sharing Unit:%
TDLOFD-00 with

eRAN

Command Name
1036 Common Actual Value Range:1~100
Carrier
Default Value:16
CellUlschAlg PreAllocationBan MOD LOFD-0010 Dynamic Meaning:Indicates the ratio of

o dwidthRatio CELLULSCHAL 1502 / Schedulin the maximum bandwidth
GO TDLOFD-00 g resources that the uplink
101502 scheduler can allocate to
LST preallocation users to the total
CELLULSCHAL system bandwidth.
GO
Unit:%
Default Value:50
CellUlschAlg PreAllocationMin MOD LOFD-0010 Dynamic Meaning:Indicates the minimum

o Period CELLULSCHAL 1502 / Schedulin interval between two
GO TDLOFD-00 g pre-allocations. That is, the
101502 actual interval between two
LST pre-allocations of one UE must
CELLULSCHAL be longer than or equal to the
GO value of this parameter.
Unit:ms
Default Value:5
CellUlschAlg PreAllocationSize MOD LOFD-0010 Dynamic Meaning:Indicates the data

o CELLULSCHAL 1502 / Schedulin amount pre-allocated to each
GO TDLOFD-00 g user.
101502
LST GUI Value Range:45~1500
CELLULSCHAL
GO Unit:byte
Default Value:80
StandardQci PreAllocationWei MOD LBFD-0020 Basic Meaning:Indicates the

ght STANDARDQCI 25 / Schedulin pre-allocation weight. The
TDLBFD-00 g pre-allocation weight of a UE is
LST 2025 the pre-allocation weight of
STANDARDQCI Enhanced services carried by the
LOFD-0010 Schedulin highest-priority logical channel.
15 / g If services carried by
TDLOFD-00
Dynamic highest-priority logical channels

eRAN

Command Name
1015 Schedulin have different pre-allocation
g weights, the UE takes the
LOFD-0010 highest pre-allocation weight.
1502 / When resources are
TDLOFD-00 insufficient, pre-allocation
101502 weights affect the pre-allocation
probabilities of users. The
pre-allocation probability has a
positive correlation with the
pre-allocation weight. This
parameter is QCI-specific.
Unit:0.1
Actual Value Range:0~1,
step:0.1
Default Value:10
StandardQci PrioritisedBitRate MOD LBFD-0020 Basic Meaning:Indicates the

STANDARDQCI 25 / Schedulin prioritized bit rate of the logical
TDLBFD-00 g channel. The UE scheduler
LST 2025 guarantees prioritized bit rates
STANDARDQCI Enhanced of logical channels in
LOFD-0010 Schedulin descending order of logical
15 / g channel priority. For details, see
TDLOFD-00
1015 Dynamic 3GPP TS 36.321.
Schedulin GUI Value
LOFD-0010 g Range:PBR_0_KBps(0KB/s),
1502 / PBR_8_KBps(8KB/s),
TDLOFD-00 PBR_16_KBps(16KB/s),
101502 PBR_32_KBps(32KB/s),
PBR_64_KBps(64KB/s),
PBR_INFINITY(Infinity)
Unit:KB/s
Actual Value
Range:PBR_0_KBps,
PBR_8_KBps, PBR_16_KBps,
PBR_32_KBps, PBR_64_KBps,
PBR_128_KBps,
PBR_256_KBps,
PBR_INFINITY
Default
Value:PBR_8_KBps(8KB/s)
PUSCHCfg Qam64Enabled MOD LOFD-0010 UL Meaning:Indicates whether

eRAN

Command Name
PUSCHCFG 06 / 64QAM 64QAM of the PUSCH is
TDLOFD-00 enabled.
LST 1006
PUSCHCFG For details, see 3GPP TS
36.211.
GUI Value
Range:BOOLEAN_FALSE(Fals
e), BOOLEAN_TRUE(True)
Unit:None
Actual Value
Range:BOOLEAN_FALSE,
BOOLEAN_TRUE
Default
Value:BOOLEAN_TRUE(True)
CellAlgoSwit RanShareModeS MOD LOFD-0010 RAN Meaning:Indicates whether to

ch witch CELLALGOSWI 36 / Sharing enable or disable eRAN sharing
TCH TDLOFD-00 with for admission and scheduling. If
1036 Common this switch is turned on,
LST Carrier operators share data channel
CELLALGOSWI LBFD-0020 resources according to the
TCH 23 / Admissio specified percentages.
TDLBFD-00 n Control
2023 GUI Value Range:OFF(Off),
Basic ON(On)
LBFD-0020 Schedulin
25 / g Unit:None
TDLBFD-00
2025 Actual Value Range:OFF, ON
Default Value:OFF(Off)
CellUlschAlg SinrAdjustTargetI MOD LBFD-0010 AMC Meaning:Indicates the target

o bler CELLULSCHAL 06 / IBLER of the SINR adjustment
GO TDLBFD-00 algorithm. A greater parameter
1006 value indicates a greater SINR
LST adjustment value, and thus a
CELLULSCHAL higher-level MCS is used.
GO
Unit:0.01
Actual Value Range:0.01~0.99,
step:0.01
Default Value:10
CellUlschAlg UlschStrategy MOD LBFD-0020 Basic Meaning:Indicates the UL

o CELLULSCHAL 25 / Schedulin scheduling policy, which
GO TDLBFD-00 g determines the scheduling
priority order in which UEs are

eRAN

Command Name
LST 2025 Enhanced arranged in UL. There are four
CELLULSCHAL Schedulin UL scheduling strategies: MAX
GO LOFD-0010 g C/I, proportional fair (PF), round
15 / Robin (RR), and enhanced
TDLOFD-00 proportional fair (EPF). The
1015 MAX C/I policy schedules UEs
in descending order of average
signal to interference plus noise
ratio (SINR). The PF policy
schedules UEs in ascending
order of ratio of the data rate to
the SINR. The RR policy
schedules each UE in
sequence, and therefore each
UE has an equal opportunity to
be scheduled. The EPF policy
schedules UEs in ascending
order of priority. In EPF, the
priority of an UE is calculated
based on the following factors:
the data rate, average SINR,
QoS-satisfying data rate for
each service, and service
differentiation requirements of
the UE. The MAX C/I, PF, and
RR policies are basic UL
scheduling policies and
supported by the eNodeB by
default, whereas the EPF policy
is intended for commercial use.
GUI Value
Range:ULSCH_STRATEGY_E
PF(EPF),
ULSCH_STRATEGY_MAX_CI(
MAX_CI),
ULSCH_STRATEGY_PF(PF),
ULSCH_STRATEGY_RR(RR)
Unit:None
Actual Value
Range:ULSCH_STRATEGY_E
PF,
ULSCH_STRATEGY_MAX_CI,
ULSCH_STRATEGY_PF,
ULSCH_STRATEGY_RR
Default
Value:ULSCH_STRATEGY_EP
F(EPF)
CellAlgoSwit UlSchSwitch MOD LBFD-0020 Basic Meaning:Indicates the switches

eRAN

Command Name
ch CELLALGOSWI 25 / Schedulin related to uplink (UL)
TCH TDLBFD-00 g scheduling in the cell. The
2025 switches are used to enable or
LST Enhanced disable specific UL scheduling
CELLALGOSWI LOFD-0010 Schedulin functions.
TCH 15 / g
TDLOFD-00 SpsSchSwitch: Indicates
1015 VoIP whether to enable or disable
Semi-pers semi-persistent scheduling
LOFD-0010 istent during talk spurts of VoIP
16 / Schedulin services. If this switch is turned
TDLOFD-00 g on, semi-persistent scheduling
1016
UL 2x2 is applied. If this switch is
LOFD-0010 MU-MIM turned off, dynamic scheduling
02 / O is applied.
LOFD-0010 SinrAdjustSwitch: Indicates
02 UL 2x4
MU-MIM whether to adjust the measured
LOFD-0010 O SINR based on ACK/NACK
58 / messages in a UL HARQ
LOFD-0010 TTI process.
58 Bundling
PreAllocationSwitch: Indicates
LOFD-0010 800M whether to enable or disable
48 / Self-interf preallocation, which shortens
TDLOFD-00 erence end-to-end service delays when
1048 Cancellati the UL load is light.
on Preallocation reduces the
LOFD-0010 probability of UEs entering DRX
67 and therefore shortens the
service time of the UEs.
UlVmimoSwitch: Indicates
whether to enable or disable UL
MU-MIMO. If UL MU-MIMO is
enabled, the eNodeB selects
UEs for pairing according to
pairing rules. Then, the pair of
UEs transmits data using the
same frequency-time
resources, increasing system
throughput and spectral
efficiency.
TtiBundlingSwitch: Indicates
whether to enable or disable
TTI bundling. If TTI bundling is
enabled, more transmission
opportunities are available to
UEs within the delay budget for
VoIP services on the air
interface, thereby improving
uplink coverage.

eRAN

Command Name
ImIcSwitch: Indicates whether
to enable or disable
intermodulation (IM) component
elimination for UEs. When data
is transmitted in both UL and
DL, two IM components are
generated symmetrically beside
the Direct Current (DC)
subcarrier on the DL receive
channel due to interference
from UL radio signals. If this
switch is turned on, IM
component elimination is
performed on UEs. If this switch
is turned off, IM component
elimination is not performed on
UEs. This switch applies only to
FDD cells working in band 20.
GUI Value
Range:SpsSchSwitch(SpsSchS
witch),
SinrAdjustSwitch(SinrAdjustSwi
tch),
PreAllocationSwitch(PreAllocati
onSwitch),
UlVmimoSwitch(UlVmimoSwitc
h),
TtiBundlingSwitch(TtiBundlingS
witch), ImIcSwitch(ImIcSwitch)
Unit:None
Actual Value
Range:SpsSchSwitch,
SinrAdjustSwitch,
PreAllocationSwitch,
UlVmimoSwitch,
TtiBundlingSwitch, ImIcSwitch
Default
Value:SpsSchSwitch:Off,
SinrAdjustSwitch:On,
PreAllocationSwitch:On,
UlVmimoSwitch:Off,
TtiBundlingSwitch:Off,
ImIcSwitch:Off
CqiAdaptive UserCqiPeriodCf MOD LBFD-0020 Basic Meaning:Indicates the fixed CQI

Cfg g CQIADAPTIVE 25 / Schedulin reporting period. A fixed CQI
CFG TDLBFD-00 g reporting period is used when
2025 CQI reporting period adaptation
LST is disabled. If the
CQIADAPTIVE

eRAN

Command Name
CFG UserCqiPeriodCfg parameter is
set to 32 ms, the eNodeB
automatically changes the value
to 20 ms. If the
UserCqiPeriodCfg parameter is
to 40 ms. If the
UserCqiPeriodCfg parameter is
to 80 ms.This parameter is valid
only for FDD cells.
GUI Value Range:ms2(2ms),
ms5(5ms), ms10(10ms),
ms20(20ms), ms32(32ms),
ms40(40ms), ms64(64ms),
ms80(80ms), ms128(128ms),
ms160(160ms)
Unit:ms
Actual Value Range:ms2, ms5,
ms10, ms20, ms32, ms40,
ms64, ms80, ms128, ms160
Default Value:ms40(40ms)

eRAN
Scheduling 14 Counters
14 Counters
Table 14-1 Counter description
Counter ID Counter Name Counter Feature ID Feature
Description Name
1526726737 L.ChMeas.PRB.UL.Used.Avg Average LBFD-002025 Basic

number of Scheduling
used uplink TDLBFD-002025
PRBs Basic
Scheduling
1526726740 L.ChMeas.PRB.DL.Used.Avg Average LBFD-002025 Basic

used downlink TDLBFD-002025
PRBs Basic
Scheduling
1526726776 L.Thrp.bits.UL.QCI.1 Uplink traffic LBFD-002008 Radio

volume for Bearer
PDCP SDUs of TDLBFD-002008 Management
services with LBFD-002025
the QCI of 1 in Radio
a cell TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic
Scheduling
1526726777 L.Thrp.Time.UL.QCI.1 Receive LBFD-002008 Radio

duration of Bearer
uplink PDCP TDLBFD-002008 Management
SDUs for LBFD-002025
services with Radio
the QCI of 1 in TDLBFD-002025 Bearer
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic

eRAN

Description Name
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management

eRAN

Description Name
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Bearer

eRAN

Description Name
a cell TDLBFD-002025 Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
services with
Radio

eRAN

Description Name
the QCI of 8 in LBFD-002025 Bearer
a cell Management
TDLBFD-002025
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
services with Radio
a cell Management
Basic
Scheduling
Basic
Scheduling
1526726803 L.Thrp.bits.DL.QCI.1 Downlink traffic LBFD-002008 Radio

volume for Bearer

eRAN

Description Name
services with LBFD-002025 Radio
the QCI of 1 in Bearer
a cell TDLBFD-002025 Management
Basic
Scheduling
Basic
Scheduling
1526726804 L.Thrp.Time.DL.QCI.1 Transmit LBFD-002008 Radio

duration of Bearer
downlink TDLBFD-002008 Management
PDCP SDUs LBFD-002025
for services Radio
with the QCI of TDLBFD-002025 Bearer
1 in a cell Management
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

volume for Bearer

eRAN

Description Name
services with
the QCI of 3 in LBFD-002025 Radio
a cell Bearer
TDLBFD-002025 Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

eRAN

Description Name

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic

eRAN

Description Name
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling

eRAN

Description Name
Basic
Scheduling

volume for Bearer
Management
Basic
Scheduling
Basic
Scheduling

duration of Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling
1526726833 L.PDCP.Tx.Disc.Trf.SDU.QCI.1 Number of LBFD-002008 Radio

downlink traffic Bearer
SDUs TDLBFD-002008 Management
discarded by LBFD-002025
the PDCP Radio
layer for TDLBFD-002025 Bearer
services with Management
the QCI of 1 in Basic
a cell Scheduling
Basic
Scheduling

the PDCP Radio

eRAN

Description Name
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling

the PDCP Radio

eRAN

Description Name
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling

the PDCP Radio
a cell Scheduling
Basic
Scheduling
1526727045 L.Thrp.bits.UL.QCI.1.Max Maximum LBFD-002008 Radio

uplink traffic Bearer
volume for TDLBFD-002008 Management
received LBFD-002025
PDCP SDUs of Radio
services with Bearer

eRAN

Description Name
the QCI of 1 in TDLBFD-002025 Management
a cell
Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
services with TDLBFD-002025 Bearer
the QCI of 2 in Management
a cell Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
a cell Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
a cell Basic
Scheduling
Basic
Scheduling

received
Radio

eRAN

Description Name
PDCP SDUs of LBFD-002025 Bearer
the QCI of 5 in TDLBFD-002025
a cell Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
a cell Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
a cell Basic
Scheduling
Basic
Scheduling

PDCP SDUs of Radio
a cell Basic
Scheduling
Basic
Scheduling


eRAN

Description Name
received LBFD-002025 Radio
PDCP SDUs of Bearer
services with TDLBFD-002025 Management
the QCI of 9 in
a cell Basic
Scheduling
Basic
Scheduling
1526727054 L.Thrp.bits.UL.Max Maximum LBFD-002008 Radio

PDCP SDUs of Radio
all services TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic
Scheduling
1526727055 L.Thrp.bits.DL.QCI.1.Max Maximum LBFD-002008 Radio

PDCP SDUs of LBFD-002025
the service Radio
with QCI of 1 in TDLBFD-002025 Bearer
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling


eRAN

Description Name
PDCP SDUs of
the service LBFD-002025 Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

eRAN

Description Name

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling

the service Radio
a cell Management
Basic
Scheduling
Basic
Scheduling
1526727064 L.Thrp.bits.DL.Max Maximum LBFD-002008 Radio

all services Radio
TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic

eRAN

Description Name
Scheduling
1526727352 L.Traffic.BCH.TB.bits Size of TBs LBFD-002002 Transport

Transmitted Channel
over the BCH LBFD-001005 Management
TDLBFD-002002 Modulation:
TDLBFD-001005 DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727353 L.Traffic.PCH.TB.bits Size of TBs LBFD-002002 Transport

Transmitted Channel
over the PCH LBFD-001005 Management
TDLBFD-002002 Modulation:
TDLBFD-001005 DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727354 L.Traffic.DL.SCH.QPSK.TB Number of TBs LBFD-002002 Transport

initially Channel
transmitted LBFD-001005 Management
over the TDLBFD-002002 Modulation:
downlink SCH
in QPSK TDLBFD-001005 DL/UL
modulation QPSK,

eRAN

Description Name
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727355 L.Traffic.DL.SCH.16QAM.TB Number of TBs LBFD-002002 Transport

initially Channel
downlink SCH
in 16QAM TDLBFD-001005 DL/UL
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727356 L.Traffic.DL.SCH.64QAM.TB Number of TBs LBFD-002002 Transport

initially Channel
downlink SCH
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL

eRAN

Description Name
QPSK,
DL/UL
16QAM, DL
64QAM
1526727357 L.Traffic.DL.SCH.QPSK.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
downlink SCH
in QPSK TDLBFD-001005 DL/UL
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727358 L.Traffic.DL.SCH.16QAM.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
downlink SCH
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727359 L.Traffic.DL.SCH.64QAM.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
over the

eRAN

Description Name
downlink SCH TDLBFD-002002 Modulation:
in 64QAM DL/UL
modulation TDLBFD-001005 QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727360 L.Traffic.DL.SCH.QPSK.TB.Retrans Number of TBs LBFD-002002 Transport

retransmitted Channel
over the LBFD-001005 Management
downlink SCH TDLBFD-002002
in QPSK Modulation:
modulation TDLBFD-001005 DL/UL
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727361 L.Traffic.DL.SCH.16QAM.TB.Retrans Number of TBs LBFD-002002 Transport

in 16QAM Modulation:
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel

eRAN

Description Name
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727362 L.Traffic.DL.SCH.64QAM.TB.Retrans Number of TBs LBFD-002002 Transport

in 64QAM Modulation:
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727363 L.Traffic.DL.SCH.QPSK.TB.Retrans.bits Size of TBs LBFD-002002 Transport

in QPSK
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name
1526727364 L.Traffic.DL.SCH.16QAM.TB.Retrans.bits Size of TBs LBFD-002002 Transport

in 16QAM
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727365 L.Traffic.DL.SCH.64QAM.TB.Retrans.bits Size of TBs LBFD-002002 Transport

in 64QAM
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727366 L.Traffic.UL.SCH.QPSK.TB Number of TBs LBFD-002002 Transport

initially Channel
over the uplink TDLBFD-002002
SCH in QPSK Modulation:
mode QPSK,
DL/UL
16QAM, DL

eRAN

Description Name
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727367 L.Traffic.UL.SCH.16QAM.TB Number of TBs LBFD-002002 Transport

initially Channel
SCH in Modulation:
16QAM TDLBFD-001005 DL/UL
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727368 L.Traffic.UL.SCH.64QAM.TB Number of TBs LBFD-002002 Transport

initially Channel
transmitted LOFD-001006 Management
SCH in UL 64QAM
64QAM TDLOFD-001006 Transport
modulation Channel
mode Management
UL 64QAM
1526727369 L.Traffic.UL.SCH.QPSK.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
over the uplink TDLBFD-002002 Modulation:
SCH in QPSK
QPSK,

eRAN

Description Name
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727370 L.Traffic.UL.SCH.16QAM.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
over the uplink TDLBFD-002002 Modulation:
SCH in
16QAM TDLBFD-001005 DL/UL
modulation QPSK,
mode DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727371 L.Traffic.UL.SCH.64QAM.TB.bits Size of TBs LBFD-002002 Transport

initially Channel
transmitted LOFD-001006 Management
over the uplink TDLBFD-002002 UL 64QAM
SCH in
64QAM TDLOFD-001006 Transport
modulation Channel
mode Management
UL 64QAM
1526727372 L.Traffic.UL.SCH.QPSK.TB.Retrans Number of TBs LBFD-002002 Transport

over the uplink LBFD-001005 Management
SCH in QPSK TDLBFD-002002
modulation Modulation:

eRAN

Description Name
mode TDLBFD-001005 DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727373 L.Traffic.UL.SCH.16QAM.TB.Retrans Number of TBs LBFD-002002 Transport

SCH in TDLBFD-002002 Modulation:
16QAM
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727374 L.Traffic.UL.SCH.64QAM.TB.Retrans Number of TBs LBFD-002002 Transport

over the uplink LOFD-001006 Management
SCH in TDLBFD-002002 UL 64QAM
64QAM
modulation TDLOFD-001006 Transport
mode Channel
Management
UL 64QAM
1526727375 L.Traffic.UL.SCH.QPSK.TB.Retrans.bits Size of TBs LBFD-002002 Transport

over the uplink LBFD-001005

eRAN

Description Name
SCH in QPSK TDLBFD-002002 Management
modulation
mode TDLBFD-001005 Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727376 L.Traffic.UL.SCH.16QAM.TB.Retrans.bits Size of TBs LBFD-002002 Transport

SCH in TDLBFD-002002 Modulation:
16QAM
mode QPSK,
DL/UL
16QAM, DL
64QAM
Transport
Channel
Management
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM
1526727377 L.Traffic.UL.SCH.64QAM.TB.Retrans.bits Size of TBs LBFD-002002 Transport

over the uplink LOFD-001006 Management
SCH in TDLBFD-002002 UL 64QAM
64QAM
modulation TDLOFD-001006 Transport
mode Channel
Management
UL 64QAM

eRAN

Description Name
1526727388 L.DLPwr.Max Maximum LBFD-002025 Basic

downlink Scheduling
transmit power TDLBFD-002025
in a cell Basic
Scheduling
1526727389 L.DLPwr.Avg Average LBFD-002025 Basic

downlink Scheduling
transmit power TDLBFD-002025
in a cell Basic
Scheduling
1526727391 L.ChMeas.MIMO.PRB.CL.Rank1 Total number LBFD-002025 Basic

of used Scheduling
downlink PRBs TDLBFD-002025
in closed-loop LOFD-001001 Basic
rank 1 mode Scheduling
LOFD-001003 DL 2x2
LOFD-001060 MIMO
DL 4x2
MIMO
DL 4X4
MIMO

of used Scheduling
LOFD-001003 DL 2x2
LOFD-001060 MIMO
DL 4x2
MIMO
DL 4X4
MIMO
1526727393 L.ChMeas.MIMO.PRB.OL.Rank1 Total number LBFD-002025 Basic

of used Scheduling
in open-loop LOFD-001001 Basic
LOFD-001003 DL 2x2
LOFD-001060 MIMO
DL 4x2
MIMO
DL 4X4

eRAN

Description Name
MIMO

of used Scheduling
LOFD-001003 DL 2x2
LOFD-001060 MIMO
DL 4x2
MIMO
DL 4X4
MIMO
1526727396 L.ChMeas.CQI.DL.0 Number of LBFD-002016 Dynamic

reports with Downlink
wideband CQI LBFD-002025 Power
of 0 TDLBFD-002016 Allocation
TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling


eRAN

Description Name
TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power

eRAN

Description Name
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

eRAN

Description Name

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

Basic

eRAN

Description Name
TDLBFD-002025 Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation
Basic
Scheduling

TDLBFD-002025 Basic
Scheduling
Dynamic
Downlink
Power
Allocation

eRAN

Description Name
Basic
Scheduling
1526727412 L.ChMeas.PUSCH.MCS.0 Number of LBFD-002025 Basic

times MCS Scheduling
index 0 is LBFD-001005
scheduled on TDLBFD-002025 Modulation:
the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic

eRAN

Description Name
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

DL/UL

eRAN

Description Name
the PUSCH TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PUSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name
1526727444 L.ChMeas.PDSCH.MCS.0 Number of LBFD-002025 Basic

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:

eRAN

Description Name
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL

eRAN

Description Name
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

the PDSCH DL/UL
TDLBFD-001005 QPSK,
DL/UL
16QAM, DL
64QAM
Basic
Scheduling
Modulation:
DL/UL
QPSK,
DL/UL
16QAM, DL
64QAM

eRAN

Description Name
1526727483 L.ChMeas.PRB.PUCCH.Avg Average LBFD-002025 Basic

used PRBs TDLBFD-002025
over the Basic
PUCCH Scheduling
1526727849 L.Thrp.bits.UL.PLMN.QCI.1 Total uplink LBFD-002008 Radio

traffic volume Bearer
for PDCP LOFD-001036 Management
SDUs of a LOFD-001037
specified RAN Sharing
operator for LBFD-002025 with
services with Common
the QCI of 1 in TDLBFD-002008 Carrier
a cell TDLOFD-001036 RAN Sharing
with
TDLOFD-001037 Dedicated
TDLBFD-002025 Carrier
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526727850 L.Thrp.Time.UL.PLMN.QCI.1 Receive LBFD-002008 Radio

duration of Bearer
uplink PDCP LOFD-001036 Management
with

eRAN

Description Name
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526727889 L.PDCP.Tx.TotRev.Trf.SDU.QCI.1 Number of LBFD-002008 Radio

eRAN

Description Name
transmitted TDLBFD-002008 Bearer
downlink traffic Management
for services Radio
with the QCI of
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
downlink traffic TDLBFD-002008 Management
for services Radio
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

eRAN

Description Name

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic

eRAN

Description Name
Scheduling

transmitted Bearer
for services Radio
Basic
Scheduling
Basic
Scheduling
1526727907 L.Traffic.DL.PktDelay.Time.QCI.1 Processing LBFD-002008 Radio

delay of Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling
1526727908 L.Traffic.DL.PktDelay.Num.QCI.1 Number of LBFD-002008 Radio

successfully Bearer
transmitted TDLBFD-002008 Management
downlink LBFD-002025
PDCP SDUs Radio
for DRB TDLBFD-002025 Bearer
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic
Scheduling

eRAN

Description Name
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic

eRAN

Description Name
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio

eRAN

Description Name
a cell Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio

eRAN

Description Name
a cell
Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling

delay of Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

successfully Bearer
PDCP SDUs Radio
a cell Scheduling
Basic
Scheduling
1526727934 L.Traffic.DL.PktUuLoss.Loss.QCI.1 Number of LBFD-002008 Radio

discarded Bearer
PDCP SDUs
Radio

eRAN

Description Name
for DRB LBFD-002025 Bearer
a cell over the Basic
Uu interface Scheduling
Basic
Scheduling
1526727935 L.Traffic.DL.PktUuLoss.Tot.QCI.1 Number of LBFD-002008 Radio

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer

eRAN

Description Name
PDCP SDUs LBFD-002025 Radio
for DRB Bearer
services with TDLBFD-002025 Management
the QCI of 3 in
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer

eRAN

Description Name
PDCP SDUs
for DRB LBFD-002025 Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

eRAN

Description Name

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic

eRAN

Description Name
Scheduling

discarded Bearer
for DRB Radio
Basic
Scheduling

transmitted Bearer
for DRB Radio
Basic
Scheduling
1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1 Number of LBFD-002008 Radio

discarded Bearer
uplink traffic TDLBFD-002008 Management
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling
1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1 Number of LBFD-002008 Radio

expected Bearer
data packets LBFD-002025
for DRB Radio
a cell Basic
Scheduling

eRAN

Description Name
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio
a cell Basic

eRAN

Description Name
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio

eRAN

Description Name
a cell Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio

eRAN

Description Name
a cell
Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

discarded Bearer
for DRB Radio
a cell Basic
Scheduling
Basic
Scheduling

expected Bearer
data packets
Radio

eRAN

Description Name
for DRB LBFD-002025 Bearer
a cell Basic
Scheduling
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with

eRAN

Description Name
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

eRAN

Description Name

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management

eRAN

Description Name
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
the QCI of 5 in

eRAN

Description Name
a cell TDLBFD-002008 Carrier
TDLOFD-001036 RAN Sharing
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated

eRAN

Description Name
Carrier
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling

eRAN

Description Name
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

SDUs of a

eRAN

Description Name
specified LOFD-001037 RAN Sharing
operator for with
services with LBFD-002025 Common
a cell
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier

eRAN

Description Name
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
with

eRAN

Description Name
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526728050 L.Thrp.bits.DL.PLMN.QCI.1 Total downlink LBFD-002008 Radio

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

eRAN

Description Name
1526728051 L.Thrp.Time.DL.PLMN.QCI.1 Transmit LBFD-002008 Radio

duration of Bearer
downlink LOFD-001036 Management
PDCP SDUs in LOFD-001037
a cell of a RAN Sharing
specified LBFD-002025 with
operator for Common
services with TDLBFD-002008 Carrier
the QCI of 1 TDLOFD-001036 RAN Sharing
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management

eRAN

Description Name
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

the QCI of 3 in

eRAN

Description Name
a cell TDLBFD-002008 Carrier
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated

eRAN

Description Name
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling

eRAN

Description Name
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
PDCP SDUs in

eRAN

Description Name
a cell of a LOFD-001037 RAN Sharing
specified with
operator for LBFD-002025 Common
the QCI of 5
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier

eRAN

Description Name
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with

eRAN

Description Name
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

eRAN

Description Name

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
with
Basic
Scheduling
Radio
Bearer
Management

eRAN

Description Name
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration of Bearer
operator for Common
services with

eRAN

Description Name
the QCI of 9 TDLBFD-002008 Carrier
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

of used Scheduling
DL 4X4
MIMO

of used Scheduling
DL 4X4
MIMO

of used Scheduling
DL 4X4
MIMO

eRAN

Description Name

of used Scheduling
DL 4X4
MIMO
1526728232 L.Thrp.Time.Cell.DL Total duration LBFD-002008 Radio

of downlink Bearer
data TDLBFD-002008 Management
transmission in LBFD-002025
a cell Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728233 L.Thrp.Time.Cell.UL Total duration LBFD-002008 Radio

of uplink data Bearer
transmission in TDLBFD-002008 Management
a cell LBFD-002025 Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728234 L.E-RAB.SessionTime.QCI1 Duration of LBFD-002008 Radio

data Bearer
transmission TDLBFD-002008 Management
for services LBFD-002025
with the QCI of Radio
1 in a cell TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
transmission

eRAN

Description Name
for services TDLBFD-002008 Management
with the QCI of
2 in a cell LBFD-002025 Radio
Bearer
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

eRAN

Description Name

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic
Scheduling

data Bearer
Management
Basic
Scheduling
Basic

eRAN

Description Name
Scheduling
1526728243 L.E-RAB.SessionTime.UE Total duration LBFD-002008 Radio

of UE data Bearer
transmission in TDLBFD-002008 Management
a cell LBFD-002025 Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728259 L.Thrp.bits.UL Total uplink LBFD-002008 Radio

for PDCP TDLBFD-002008 Management
SDUs in a cell LBFD-002025
Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728260 L.Thrp.Time.UL Total receive LBFD-002008 Radio

duration of Bearer
Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728261 L.Thrp.bits.DL Total downlink LBFD-002008 Radio

for PDCP TDLBFD-002008 Management
Radio
Management
Basic
Scheduling

eRAN

Description Name
Basic
Scheduling
1526728262 L.Thrp.Time.DL Total transmit LBFD-002008 Radio

duration of Bearer
PDCP SDUs in LBFD-002025
a cell Radio
Management
Basic
Scheduling
Basic
Scheduling
1526728263 L.Thrp.bits.UL.PLMN Total uplink LBFD-002008 Radio

operator in a LBFD-002025 with
cell Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526728264 L.Thrp.Time.UL.PLMN Total receive LBFD-002008 Radio

duration of Bearer
SDUs of a

eRAN

Description Name
specified LOFD-001037 RAN Sharing
operator in a with
cell LBFD-002025 Common
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526728265 L.Thrp.bits.DL.PLMN Total downlink LBFD-002008 Radio

operator in a LBFD-002025 with
cell Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier

eRAN

Description Name
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526728266 L.Thrp.Time.DL.PLMN Total transmit LBFD-002008 Radio

duration of Bearer
operator Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526728293 L.RBUsedOwn.DL.PLMN Number of LBFD-002025 Basic

PDSCH PRBs Scheduling
used by a TDLBFD-002023
specified Admission
LOFD-001036 Control
operator within
its allocated LOFD-001037 RAN Sharing
PRB with
proportion in a Common
cell Carrier
RAN Sharing
with

eRAN

Description Name
Dedicated
Carrier
1526728294 L.RBUsedOwn.UL.PLMN Number of LBFD-002025 Basic

PUSCH PRBs Scheduling
specified Congestion
LOFD-001036 Control
operator within
its allocated LOFD-001037 RAN Sharing
PRB with
cell Carrier
RAN Sharing
with
Dedicated
Carrier
1526728295 L.RBUsedOther.DL.PLMN Number of LBFD-002025 Basic

PDSCH PRBs Scheduling
specified Basic
LOFD-001036 Scheduling
operator
exceeding its LOFD-001037 RAN Sharing
allocated PRB with
cell Carrier
RAN Sharing
with
Dedicated
Carrier
1526728296 L.RBUsedOther.UL.PLMN Number of LBFD-002025 Basic

PUSCH PRBs Scheduling
specified Uplink
LOFD-001036 Power
operator
exceeding its LOFD-001037 Control
allocated PRB RAN Sharing
proportion in a with
cell Common
Carrier
RAN Sharing
with
Dedicated
Carrier
1526729005 L.Thrp.bits.DL.LastTTI Downlink traffic LBFD-002008 Radio

volume sent in Bearer

eRAN

Description Name
the last TTI TDLBFD-002008 Management
before the
buffer is empty LBFD-002025 Radio
Bearer
Basic
Scheduling
Basic
Scheduling
1526729006 L.Thrp.bits.DL.LastTTI.QCI.1 Downlink traffic LBFD-002008 Radio

the last TTI for TDLBFD-002008 Management
the QCI 1 Radio
before the TDLBFD-002025 Bearer
buffer is empty Management
Basic
Scheduling
Basic
Scheduling

the QCI 2 Radio
Basic
Scheduling
Basic
Scheduling

the QCI 3 Radio
Basic
Scheduling
Basic
Scheduling

eRAN

Description Name

the QCI 4 Radio
Basic
Scheduling
Basic
Scheduling

the QCI 5 Radio
Basic
Scheduling
Basic
Scheduling

the QCI 6 Radio
Basic
Scheduling
Basic
Scheduling

the QCI 7 Radio
Basic
Scheduling
Basic

eRAN

Description Name
Scheduling

the QCI 8 Radio
Basic
Scheduling
Basic
Scheduling

the QCI 9 Radio
Basic
Scheduling
Basic
Scheduling
1526729015 L.Thrp.Time.DL.RmvLastTTI Data transmit LBFD-002008 Radio

duration Bearer
except the last TDLBFD-002008 Management
TTI before the LBFD-002025
downlink buffer Radio
is empty TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic
Scheduling
1526729016 L.Thrp.Time.DL.RmvLastTTI.QCI.1 Data transmit LBFD-002008 Radio

duration Bearer
is empty for TDLBFD-002025 Bearer
the QCI 1 Basic
Scheduling

eRAN

Description Name
Basic
Scheduling

duration Bearer
the QCI 2 Basic
Scheduling
Basic
Scheduling

duration Bearer
the QCI 3 Basic
Scheduling
Basic
Scheduling

duration Bearer
the QCI 4 Basic
Scheduling
Basic
Scheduling

duration Bearer
the QCI 5 Basic

eRAN

Description Name
Scheduling
Basic
Scheduling

duration Bearer
the QCI 6 Basic
Scheduling
Basic
Scheduling

duration Bearer
the QCI 7 Basic
Scheduling
Basic
Scheduling

duration Bearer
the QCI 8 Basic
Scheduling
Basic
Scheduling

duration Bearer

eRAN

Description Name
the QCI 9 Basic
Scheduling
Basic
Scheduling
1526729025 L.Thrp.bits.DL.LastTTI.PLMN Downlink traffic LBFD-002008 Radio

the last TTI LOFD-001036 Management
before the LOFD-001037 RAN Sharing
buffer is empty
for a specific LBFD-002025 with
operator Common
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526729026 L.Thrp.bits.DL.LastTTI.PLMN.QCI.1 Downlink traffic LBFD-002008 Radio

buffer is empty
for services LBFD-002025 with
with the QCI 1 Common
for a specific TDLBFD-002008 Carrier
operator TDLOFD-001036 RAN Sharing
with
Basic

eRAN

Description Name
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling


eRAN

Description Name
before the
buffer is empty LOFD-001037 RAN Sharing
for services with
LBFD-002025 Common
with the QCI 3
operator
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common

eRAN

Description Name
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with

eRAN

Description Name
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic

eRAN

Description Name
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

buffer is empty
with
Basic
Scheduling
Radio
Bearer

eRAN

Description Name
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526729035 L.Thrp.Time.DL.RmvLastTTI.PLMN Data transmit LBFD-002008 Radio

duration Bearer
except the last LOFD-001036 Management
TTI before the LOFD-001037
downlink buffer RAN Sharing
is empty for a LBFD-002025 with
specific Common
operator TDLBFD-002008 Carrier
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526729036 L.Thrp.Time.DL.RmvLastTTI.PLMN.QCI.1 Data transmit LBFD-002008 Radio

duration Bearer
is empty for with

eRAN

Description Name
services with LBFD-002025 Common
the QCI 1 for a Carrier
specific TDLBFD-002008
operator RAN Sharing
TDLOFD-001036 with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
is empty for LBFD-002025 with
the QCI 2 for a TDLBFD-002008 Carrier
specific TDLOFD-001036 RAN Sharing
operator with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with

eRAN

Description Name
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with
Basic

eRAN

Description Name
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer

eRAN

Description Name
TTI before the
downlink buffer LOFD-001037 RAN Sharing
is empty for with
LBFD-002025 Common
services with
specific
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common

eRAN

Description Name
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

duration Bearer
operator with

eRAN

Description Name
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526729049 L.Thrp.bits.UE.UL.LastTTI Traffic volume LBFD-002008 Radio

of uplink PDCP Bearer
SDUs sent in TDLBFD-002008 Management
the last TTI LBFD-002025
before the UE Radio
buffer is empty TDLBFD-002025 Bearer
Management
Basic
Scheduling
Basic
Scheduling
1526729050 L.Thrp.Time.UE.UL.RmvLastTTI Uplink data LBFD-002008 Radio

transmit Bearer
duration TDLBFD-002008 Management
except the last LBFD-002025
TTI before the Radio
UE buffer is TDLBFD-002025 Bearer
empty Management
Basic
Scheduling
Basic
Scheduling
1526729051 L.Thrp.bits.UE.UL.LastTTI.PLMN Traffic volume LBFD-002008 Radio

of uplink PDCP Bearer
SDUs sent in LOFD-001036 Management
the last TTI

eRAN

Description Name
before the UE LOFD-001037 RAN Sharing
buffer is empty with
for a specific LBFD-002025 Common
operator TDLBFD-002008 Carrier
with
Carrier
TDLBFD-002025
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling
1526729052 L.Thrp.Time.UE.UL.RmvLastTTI.PLMN Uplink data LBFD-002008 Radio

transmit Bearer
duration LOFD-001036 Management
except the last LOFD-001037
TTI before the RAN Sharing
UE buffer is LBFD-002025 with
empty for a Common
specific TDLBFD-002008 Carrier
with
Basic
Scheduling
Radio
Bearer
Management
RAN Sharing
with
Common
Carrier

eRAN

Description Name
RAN Sharing
with
Dedicated
Carrier
Basic
Scheduling

eRAN
Scheduling 15 Glossary
15 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Scheduling 16 Reference Documents
16 Reference Documents
This chapter lists the reference documents related to scheduling.
[1] 3GPP TS 36.213, "Physical layer procedures"
[2] 3GPP TS 36.211, "Physical Channels and Modulation"
[3] 3GPP TS 36.321, "Medium Access Control (MAC) protocol specification"
[4] 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
[5] 3GPP TS 23.203, "Technical Specification Group Services and System Aspects; Policy and
charging control architecture"
[6] eNodeB Performance Counter Reference
[7] eNodeB MO Reference
[8] eNodeB Initial Configuration Guide
[9] eNodeB Reconfiguration Guide
[10] DRX Feature Parameter Description
[11] ICIC Feature Parameter Description


Scheduling (eRAN3.0 06)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scheduling (eRAN3.0 06)

Uploaded by

Copyright:

Available Formats

Scheduling

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

4 DL Enhanced Scheduling .......................................................................................................4-1

Issue 06 (2013-05-20) Huawei Proprietary and Confidential i

5.3 UL Dynamic Scheduling for Initial Transmissions ......................................................................... 5-5

6 UL Enhanced Scheduling .......................................................................................................6-1

7 Cooperation with Other Features .........................................................................................7-1

8 Related Features and Their Impacts on the Network ......................................................8-1

9 Engineering Guidelines for DL Basic Scheduling ...........................................................9-1

10 Engineering Guidelines for DL Enhanced Scheduling ...............................................10-1

Issue 06 (2013-05-20) Huawei Proprietary and Confidential ii

10.1.2 LOFD-00101502 Dynamic Scheduling ............................................................................. 10-1

11 Engineering Guidelines for UL Basic Scheduling .......................................................11-1

12 Engineering Guidelines for UL Enhanced Scheduling ...............................................12-1

Issue 06 (2013-05-20) Huawei Proprietary and Confidential iii

12.4.4 Initial Configuration ........................................................................................................... 12-2

Issue 06 (2013-05-20) Huawei Proprietary and Confidential iv

1.2 Intended Audience

1.3 Change History

Change Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-1

Change Change Description Parameter Change

Change Change Description Parameter Change

Change Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-2

Change Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-3

Change Type Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-4

2.2 Features Involved in Scheduling

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-1

Table 2-2 Features involved in scheduling

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-2

LBFD-002005 DL Asynchronous HARQ

LBFD-002025 Basic Scheduling

LBFD-002031 Support of Aperiodic CQI Reports

2.3.2 DL Enhanced Scheduling

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-3

LOFD-00101502 Dynamic Scheduling

2.3.3 UL Basic Scheduling

LBFD-002006 UL Synchronous HARQ

2.3.4 UL Enhanced Scheduling

LOFD-001048 TTI Bundling

TTI bundling is not supported in a cell with 1.4 MHz bandwidth.

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-4

RI: rank indication PMI: precoding matrix indication

DL basic scheduling involves the following features:

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-1

Channel State Information

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-2

3.1.2 Basic Functions

3.1.4 Procedure for DL Scheduling in Each TTI

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-3

Figure 3-2 Overall procedure for DL scheduling

In the procedure, the eNodeB takes the following actions:

3.2 Scheduling Common Control Information

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-4

3.3 Scheduling for DL Retransmissions