ZTE LTE FDD MAC Feature Guide PDF

ZTE LTE FDD MAC Feature Guide
Version Date Author Reviewer Notes
Add the following features:

MBR > GBR in R10
Huang
V1.0 2016-03-30 Tan Wei Small Packets service optimization
Kung
NI based interference avoidance scheduling
TCP RTT optimization
Update the version number
Huang
Add the parameters in the technical
V1.1 2016-09-20 Tan Wei description
Kung
In Section 3.2.8.2, add some description
about the path loss
© 2016 ZTE Corporation. All rights reserved.
ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without
the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to change
without notice.
TABLE OF CONTENTS
1 Introduction
1.1 Feature Attribute
1.2 Related Feature List and License Control
1.3 Correlation with Other Features
2 Function Description
2.1 Architecture of the MAC Layer
2.2 Scheduling Principles
2.2.1 Uplink Scheduling
2.2.2 Downlink Scheduling
3 Technical Description
3.1 Definitions
3.2 Technical Details
3.2.1 Logical Channels and Transport Channels
3.2.2 Scheduling Policies
3.2.3 HARQ
3.2.4 QoS
3.2.5 Link Adaptation
3.2.6 Self-Adaptive Downlink MIMO Mode
3.2.7 Frequency Domain Scheduling
3.2.8 Uplink TTI Bundling
3.2.9 DRX
3.2.10 Random Access
3.2.11 SPS
4 Engineering Guide
4.1 Related parameters
4.1.1 Related parameters for Scheduling Policy
4.1.2 Related parameters for QoS
4.1.3 Related parameters for PDCCH and CFI Allocation
4.1.4 Related parameters for Uplink and Downlink Frequency Selection
4.1.5 Related parameters for Adaptive DL MIMO Modes
4.1.6 Related parameters for UL TTI Bundling
4.1.7 Related parameters for DRX
4.1.8 Related parameters for Scheduling in Random Access
4.1.9 Related parameters for SPS Configuration
4.2 Related Counters, KPI and Alarms
4.2.1 Related Counters
4.2.2 Related KPI
4.2.3 Related Alarms
4.3 Application Scenarios
4.3.1 Hardware Requirements
4.3.2 EPC Requirements
4.3.3 Frequency Band, Frequency and Bandwidth Requirements of Frequency Carrier
4.3.4 UE Requirement
4.3.5 Transmission Bandwidth Requirements
4.4 Parameter Configuration Procedure
4.4.1 Scheduling Policy Configuration
4.4.2 QoS Configuration
4.4.3 PDCCH and CFI Allocation Configuration
4.4.4 Link Adaptation Configuration
4.4.5 Uplink and Downlink Frequency Selection Configuration
4.4.6 Adaptive DL MIMO Modes Configuration
4.4.7 UL TTI Bundling Configuration
4.4.8 DRX Configuration
4.4.9 Scheduling in Random Access Configuration
4.4.10 SPS Configuration
5 Function Validation
5.1 Scheduling Policy Function
5.1.1 Topology
5.1.2 Test Specification
5.1.3 Test Result
5.2 QoS
5.3 PDCCH and CFI Allocation
5.3.1 Topology
5.3.3 Test Result
5.4 Adaptive DL MIMO Modes Function
5.5 Uplink and Downlink Frequency Selection Function
5.5.1 Topology
5.5.3 Test Result
5.6 UL TTI Bundling
5.6.1 Topology
5.6.3 Test Result
5.7 Long DRX Function
5.7.1 Topology
5.7.3 Test Result
5.8 Short DRX Function
5.8.1 Topology
5.8.3 Test Result
5.9 Random Access Function
5.10 SPS Function
5.10.1 Topology
5.10.3 Test Result
5.11 HARQ
5.11.1 Topology
5.11.3 Test Result
6 Abbreviations
7 Reference
FIGURES
Figure 2-1 LTE Protocol Stack

Figure 2-2 Architecture of the MAC Layer
Figure 2-3 Uplink Scheduling Flow
Figure 2-4 Downlink Scheduling Flow
Figure 3-1 Mapping Between Downlink Logical Channels and Downlink Transport Channels
Figure 3-2 Mapping Between Uplink Logical Channels and Uplink Transport Channels
Figure 3-3 FFs in the Qos SchedulerQos
Figure 3-4 Operator-Configurable QoS Scheduler
Figure 3-5 Uplink Dynamic Scheduling Flow
Figure 3-6 Adaptive PDCCH Flow
Figure 3-7 Adaptive CFI Flow
Figure 3-8 TCP RTT Optimization
Figure 3-9 AMC Function
Figure 3-10 Downlink Adaptation Flow
Figure 3-11 Uplink Adaptation Flow
Figure 3-12 Configuration Principle of Downlink Multi-Antenna Transmission Mode at the Initial
Access
Figure 3-13 TTI Bundling HARQ Time Sequence
Figure 3-14 DRX Principle
Figure 3-15 DRX Impact on Uplink Scheduling
Figure 3-16 DRX Impact on Downlink Scheduling
Figure 3-17 Msg2 and Msg3 Scheduling Sequence
Figure 3-18 UE Sending and Receiving Intervals
Figure 4-1 Open the EMLP-List tab
Figure 4-2 Configuring the Scheduler Algorithm Parameter
Figure 4-3 Configuring PDCCH and CFI Adaption Parameters
Figure 4-4 Disable the CFI and PDCCH adaption functions
Figure 4-5 Enabling the Link Adaptation Parameters
Figure 4-6 Inner AMC CQI Expire Timer Parameters
Figure 4-7 Disable Link Adaptation functions
Figure 4-8 Configuring Uplink Frequency Selection Switch Parameters
Figure 4-9 Configuring Downlink Frequency Selection Switch Parameters
Figure 4-10 Configuring QCI1 NI Frequency Select Switch Parameters
Figure 4-11 Configuring the Method of Feedbacking CQI for PUSCH
Figure 4-12 Open SRS Feature
Figure 4-13 Disable Uplink Frequency Selection
Figure 4-14 Disable Downlink Frequency Selection
Figure 4-16 Configuring Switch of TTI Bundling
Figure 4-17 Configuring other parameters for TTI Bundling test (a)
Figure 4-18 Configuring other parameters for TTI Bundling test (b)
Figure 4-19 Deactivate TTI Bundling
Figure 4-20 Configuring DRX switch Parameters
Figure 4-21 Configuring DRX Parameters
Figure 4-23 Deactivate DRX feature
Figure 4-24 Configuring RACH Parameters (a)
Figure 4-25 Configuring RACH Parameters (b)
Figure 4-26 Selecting the Uplink and Downlink EMLP parameters
Figure 4-27 Configuring Scheduler Algorithm
Figure 4-28 Configuring Number of PUCCH Channel for ACK/NACK of Downlink SPS
Scheduling
Figure 5-1 Scheduling Policy Function Verification Test Architecture
Figure 5-2 UE 1 Throughput when the 2UE PF Algorithm is Used
Figure 5-4 UE 1 Throughput when the 2UE MAX C/I Algorithm is Used
Figure 5-6 UE 1 Throughput when the 2UE ER Algorithm is Used
Figure 5-8 UE 1 Throughput when the 2UE RR Algorithm is Used
Figure 5-10 PDCCH Aggregation 1
Figure 5-12 eNodeB CFI Statistics
Figure 5-13 CFI Scheduling when a UE is Connected
Figure 5-14 CFI Scheduling when Two UEs are Attached and Initiated Services
Figure 5-15 CFI Scheduling when Services are Terminated
Figure 5-16 Uplink and Downlink Frequency Selection Test
Figure 5-17 Uplink Frequency Selection Disabled, Noise not Added
Figure 5-18 Uplink Frequency Selection Disabled, Noise Added
Figure 5-19 Uplink Frequency Selection Enabled, Noise Added
Figure 5-20 Downlink Frequency Selection Disabled, Noise not Added
Figure 5-21 Downlink Frequency Selection Disabled, Noise Added
Figure 5-22 Downlink Frequency Selection Enabled, Noise Added
Figure 5-23 Checking Whether the TTI bundling Function is Supported
Figure 5-24 Sub-Frames Scheduled Independently before the TTI Bundling Function is Enabled
Figure 5-25 Enabling the TTI Bundling Function
Figure 5-26 Sub-Frame Scheduling after TTI bundling enabled
Figure 5-27 Disabling the TTI Bundling Function
Figure 5-28 Sub-Frame Scheduling after TTI bundling is not enabled
Figure 5-29 Start and End Time of the long DRX Cycle
Figure 5-30 End Time of This DRX Cycle
Figure 5-31 End Time of onDurationTimer
Figure 5-32 Closest PDCCH Sent at Frame 223 Sub-Frame 3 After onDurationTimer is Started
Figure 5-33 UE Receives the PDCCH Message at Frame 224 Sub-Frame 4
Figure 5-34 Time When drx-InactivityTimer is Started
Figure 5-35 drx-InactivityTimer Expires
Figure 5-36 Time When the UE Receives the Final PDCCH
Figure 5-37 UE Enters active Status
Figure 5-38 UE Sends an SR Message
Figure 5-39 Starting UL_RETX_TIMER
Figure 5-40 CRC Test for PDSCH Data Received by the UE
Figure 5-41 Drx-RetransmissionTimer Started
Figure 5-42 Drx-RetransmissionTimer Stopped
Figure 5-43 The DRX information can be seen from RRC Connection Reconfiguration message
Figure 5-44 Short DRX Start Time and End Time
Figure 5-45 SPS Information Checked in RRC Connection Reconfiguration message
Figure 5-46 UE Receives the SPS Scheduling Authorization Message
Figure 5-47 UE Sends the Uplink Data for the First Time after Receiving the Scheduling
Message
Figure 5-48 PUSCH Data sent at the SPS Cycle Point (At an Interval of 20 ms)
Figure 5-49 SPS PUSCH Data Sent for the second Time
Figure 5-50 UE Receives the DCI1A Message that Activates the Downlink SPS Data
Figure 5-51 UE Receives the DCI1A Scheduling Message that Activates the Downlink SPS
Data
Figure 5-52 DL HARQ Test Result
Figure 5-53 There is a NAK in PHICH in subframe 5291
Figure 5-54 The Retransmitted data transmits on PUSCH
Figure 5-55 The Re-tx index
TABLES
Table 1-1 Related Feature List and License Control

Table 1-2 Correlated with Other Features
Table 3-1 Relationship between Msg3 TBSs and Msg3 Contents
Table 3-2 SPS C-RNTI Configurations for the PDCCH and PDSCH
Table 4-1 Rule of scheduling policy parameter configuration
Table 4-2 PDCCH and CFI allocation parameters configuration rule
Table 4-3 Rule of uplink and downlink frequency selection parameters
Table 4-4 Rule of UL TTI bundling parameter configuration
Table 4-5 Rule of DRX parameters configuration
Table 4-6 Rule of random access parameters configuration
Table 4-7 Rule of SPS parameters configuration
Table 4-8 Descriptions for PDCCH and CFI Allocation Counters
Table 4-9 Descriptions for UL TTI Bundling Counters
Table 4-10 Descriptions for Scheduling in Random Access Counters
Table 5-1 Device Required for the Scheduling Policy Function Test
Table 5-2 Scheduling Policy Function Test Specification
Table 5-3 PDCCH Self-Adaptive Test Specification
Table 5-4 CFI Self-Adaptive Test Specification
Table 5-5 Required Devices for the Uplink and Downlink Frequency Selection Function
Table 5-6 Uplink Frequency Selection Function Test Specification
Table 5-7 Downlink Frequency Selection Function Test Specification
Table 5-8 UL TTI Bundling Test Specification
Table 5-9 Long DRX Function Test
Table 5-10 Short DRX Function Test
Table 5-11 Uplink SPS Function Test Specification
Table 5-12 Downlink SPS Function Test Specification
Table 5-13 HARQ Function Test Specification
1 Introduction
This document provides the introduction, technical descriptions, parameter

configuration, counters, alarms, and validation procedure of the LTE FDD MAC
Scheduling feature.
The parameters, alarms and counters in this document are the same as those of the
latest software version when this document is released. To obtain the MO,
parameters, alarms, and KPIs of the existing software version, please refer to the
product manuals of the existing software version.
This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in
this document respectively refer to "LTE FDD" and "LTE FDD–based eNodeB".
1.1 Feature Attribute
 For FDD single-mode eNodeB V3.30.20.50 series:
EMS: V12.15. 30
OMMB: V12.15.30
 For GUL multi-mode eNodeB V4.15.10.30 series:
EMS version: V12.15.30
OMMB version: V12.15.30
Note:
FDD single-mode V3.30.20.50 corresponds to GUL multi-mode V4.15.10.30, and

LTE technology description and operation requirements in the corresponding
versions are the same.
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
√ √ √ - - - - -
Note:
*-: Not involved
*√: involved
1.2 Related Feature List and License Control
Table 1-1 Related Feature List and License Control
No Feature List No. Feature List Name License Control

or not
1 ZLF31-13-001 UL/DL HARQ No
2 ZLF31-13-002 Dynamic Scheduling No
3 UL/DL Frequency Selective No
ZLF31-13-003
Scheduling
4 ZLF31-13-005 TTI Bundling Yes
5 ZLF31-13-006 Semi-Persistent Scheduling Yes
6 ZLF31-13-007 Long DRX Yes
7 ZLF31-13-008 Short DRX Yes
8 ZLF31-13-009 QoS Scheduler No
9 ZLF31-13-011 Pseudo GBR for NGBR No
10 ZLF31-13-012 Advanced AMC No
11 ZLF31-13-013 PDCCH Link Adaptation No
12 Advanced Operator Configurable No
ZLF31-13-022
QoS Scheduler
13 ZLF31-13-034 MBR > GBR in R10 No
14 NI Based Interference No
ZLF31-13-041
Avoidance Scheduling
15 Small Packets Service No
ZLF31-13-042
Optimization
16 ZLF31-13-043 TCP RTT Optimization No
1.3 Correlation with Other Features
Table 1-2 Correlated with Other Features
Feature Feature Name Required Exclusive Affected

ID Feature Feature Feature
ZLF31-13-001 UL/DL HARQ None None None
Dynamic Scheduling ZLF31-13-009 None None
QoS Scheduler
ZLF31-13-002 ZLF31-13-013
PDCCH Link
Adaptation
UL/DL Frequency None ZLF31-03-002 None
ZLF31-13-003 Selective Scheduling High Speed
UE
Feature Feature Name Required Exclusive Affected
ID Feature Feature Feature
TTI Bundling ZLF31-03-002
ZLF31-13-001
ZLF31-13-005 High Speed None
UL/DL HARQ
UE
Semi-Persistent ZLF31-13-001
ZLF31-13-006 Scheduling None None
UL/DL HARQ
ZLF31-13-007 Long DRX None None None
Short DRX ZLF31-13-007 None None
ZLF31-13-008
Long DRX
ZLF31-13-009 QoS Scheduler None None None
Pseudo GBR for ZLF31-13-009 None None
ZLF31-13-011 NGBR QoS Scheduler
Advanced AMC ZLF31-13-001 None None
ZLF31-13-012
UL/DL HARQ
PDCCH Link None None None
ZLF31-13-013
Adaptation
Advanced Operator ZLF31-13-009 None ZLF31-15-
Configurable QoS QoS Scheduler 008 SDMA
ZLF31-13-022 Scheduler for Super
Cell
ZLF31-13-034 MBR > GBR in R10 None None None
NI Based None None
Interference
Avoidance ZLF31-13-003
Scheduling UL/DL
Frequency
Selective
Scheduling
ZLF31-13-041
ZLF31-13-019
Static ICIC
ZLF31-13-020
Dynamic ICIC
Small Packets None None None
ZLF31-13-
042
Service
Optimization
TCP RTT None None None
ZLF31-13-043
Optimization
2 Function Description
2.1 Architecture of the MAC Layer
Figure 2-1 LTE Protocol Stack
As defined in 3GPP TS 36.300, Media Access Control (MAC) is the lowest sublayer
at layer 2 of the Long Term Evolution (LTE) protocol stack, as shown in Figure 3-1.
Transport channels connect the MAC and physical layers, and define the formats
and methods for radio interfaces to transfer data. Logical channels connect the MAC
and Radio Link Control (RLC) layers, and the types of logical channels are
determined by the type of the information to be transmitted. The MAC layer
multiplexes and demultiplexes between the transport channels and the logical
channels. The MAC layer at the transmitting side receives MAC Service Data Units
(SDUs) from the logical channels and encapsulates them into MAC Packet Data
Units (PDUs), that is, transport blocks. The MAC layer at the receiving side receives
the MAC PDUs from the transport channels and decapsulates them into the original
MAC SDUs.
Figure 2-2 Architecture of the MAC Layer

As shown in figure above, the MAC layer consists of a Hybrid Automatic Report
Request (HARQ) unit, a multiplexing/demultiplexing unit, and a controller that
implements all control functions. The multiplexing/demultiplexing unit multiplexes the
data from multiple logical channels to one transport channel or demultiplexes the
data from one transport channel to multiple logical channels. If new transmission on
some logical channels is detected during scheduling, the multiplexing module
multiplexes the MAC SDUs from the logical channels into MAC PDUs. The
multiplexing determines the specified logical channels on which the data must be
included in the MAC PDUs and the size of the data prioritized on the logical channels.
After being received and properly decoded, the MAC PDUs are forwarded to the
demultiplexing module and depacketized into MAC SDUs. The MAC SDUs are then
allocated to the corresponding RLC units. In addition, in the peer communication
between the MAC layers, the control message named as MAC Control Elements can
also be included in the MAC PDUs. For the multiplexing and demultiplexing
descriptions, in the Section of Multiplexing and Mapping will be described.
The HARQ unit provides HARQ operation respectively at the receiving and
transmitting ends. The HARQ unit at the transmitting end sends and resends
transport blocks, and receives and processes ACK or NACK messages. The HARQ
unit at the receiving end receives transport blocks, reassembles the received data,
and generates ACK or NACK messages. For consecutive transmission, eight HARQ
processes are used to implement the ‘Stop-And-Wait’ (SAW) HARQ operation when
the transport blocks are being decoded. For the HARQ unit descriptions, refer to
Section of HARQ.
The controller provides Discontinuous Reception (DRX), random access channel

procedure, data scheduling, and Timing Advance (TA) maintenance. For the TA
descriptions, refer to the ZTE LTE FDD Physical Layer Procedure Feature Guide.
2.2 Scheduling Principles
MAC scheduling of the eNodeB allocates available radio resources (for example,
physical resource blocks), UE power in a cell, and radio bearer power of each UE.
The detailed scheduling algorithm is not specified in 3GPP, and is determined by
vendors in compliance with the scheduling signaling and procedures specified in the
standard protocol.
MAC scheduling is based on UE capabilities. For example, if the UE capability level

is 3, the MAC scheduler must ensure that the DL-SCH transport block of each
Transmission Time Interval (TTI) is less than or equal to 102048 bits.
In the scheduling policies, the eNodeB allocates downlink or uplink radio resources
to a UE based on the downlink Buffer Status Report (BSR) of the eNodeB or the
BSR reported by the UE. In addition, the eNodeB determines the size of a MAC PDU
according to the QoS requirement of each radio bearer. For the scheduling policy
descriptions, refer to Section of Scheduling Policies.
3GPP LTE defines the detailed QoS requirements. Based on the priority queues and
resource allocations of different UEs, eNodeB MAC scheduling must guarantee the
QoS requirements for different QoS Class Identifiers (QCIs). In configurable QoS
scheduling, a subscriber scheduling priority absolutely or relatively based on the
Allocation Retention Priority (ARP) can be provided. For the QoS scheduling
descriptions including dynamic scheduling policies, refer to section QoS. The MAC
scheduling also supports an adaptive PDCCH Control Channel Element (CCE)
aggregation level, adaptive power offset, and adaptive Control Format Indicator
(CFI).
Modulation and Coding Scheme (MCS) is determined by the Adaptive Modulation

and Coding (AMC) module. An outer AMC is used to address UE-reported errors
and adapt the radio environment that is different from link-level simulation using an
inner AMC.
Due to the fading feature of radio channels, frequency selective scheduling can be
used in a low-rate scenario depending on the specific frequency channel technology.
However, the feedback of channel quality in a high-rate scenario or low-packet
service is unreliable, and non-frequency-selective scheduling is required. Non-
frequency-selective scheduling is based on the frequency diversity of transport
blocks during transmission, instead of the special frequency channel technology.
Frequency-based adaptive scheduling is also provided.
3GPP specifies Semi-Persistent Scheduling (SPS) for voice services. SPS

configures radio resources in a semi-persistent manner and allocates radio
resources to UEs for a long time period, to prevent all subframes from being
delivered to the special downlink assignment messages or uplink authorization
messages on the PDCCH.
SPS is often used to process periodic services with packets of a small and stable
size, for example, the voice service. Compared with dynamic scheduling, the
PDCCHs are obviously decreased. Because the PDCCH resources in the LTE
network are limited, SPS greatly increases the number of activated subscribers in
the network. For the SPS descriptions, refer to section SPS.
There are seven downlink transmission antenna modes specified by 3GPP. This
current version supports the four following modes: signal antenna, transmit diversity,
open-loop spatial multiplexing, and closed-loop spatial multiplexing. Downlink
antenna modes vary in different scenarios. The algorithm for an adaptive downlink
MIMO mode is also provided to meet the requirements for different scenarios.
HARQ is retransmitted several times for cell edge subscribers in a poor radio
environment. For some short-time slot and periodic services, for example, VoIP,
HARQ retransmission results in unguaranteed service delay. Therefore, uplink TTI
bundling is used for VoIP delay at cell edges. For the TTI bundling descriptions, refer
to section Uplink TTI Bundling.
3GPP provides DRX to save the power of UEs, with the same function as the
CELL_PCH and URA_PCH in the WCDMA system. This current version only
supports long DRX. For the DRX descriptions, refer to section DRX.
For the random access descriptions, refer to section Random Access.
2.2.1 Uplink Scheduling
The figure below shows the uplink scheduling flow of ZTE eNodeB. The priority of
MSG 2 scheduling is the highest, and the priority of RB allocation is the lowest.
Figure 2-3 Uplink Scheduling Flow
MSG 2 scheduling authorizes uplink scheduling for MSG 3 transmission.
The SPS scheduling module controls VoIP services in semi-persistent scheduling

manner.
The retransmission module controls retransmission through the HARQ process. It

supports non-adaptive and adaptive modes. Non-adaptive mode is preferred for
dynamic adjustment. In non-adaptive retransmission, the position of PRB resources
and the used MCS are the same as those in the initial transmission, and the only
difference is the RV versions. If the same PRB resource position as that in the initial
transmission cannot be detected during the non-adaptive retransmission, adaptive
retransmission is attempted.
The SR response module receives a Scheduling Request (SR) message from a UE

through the PUCCH, and allocates a default authorization with PRB being 2 and
MCS being 2 to the UE.
The Dedicated Control Channel (DCCH) scheduling module checks whether there
is a Signaling Radio Bearer (SRB) transmission request from a UE. If the request
exists, the module calculates the size of all SRB1 and SRB2 buffers and then
allocates the number of PRBs that is three fewer than that of the current MCSs.
The QoS scheduling module manages diversified services from subscribers based
on scheduling priority parameters. In addition, the AMC function determines the
number of PRBs and the MCS.
The RB allocation module allocates PRB positions based on dynamic frequency-

domain scheduling. The frequency-domain scheduling includes Frequency-domain
Selective Scheduling (FSS) and Non-Frequency-domain Selective Scheduling
(NFSS).
MAC statistics refers to MAC scheduling statistics. The module sends the statistical
result to the Operation, Administration and Maintenance (OAM) module for KPI
information collection.
2.2.2 Downlink Scheduling
The figure below shows the downlink scheduling flow of ZTE eNodeB. The priority
of BCCH/CCCH/PCCH scheduling is the highest, and the priorities of RB allocation
and KPI data collection are the lowest.
Figure 2-4 Downlink Scheduling Flow
The BCCH/CCCH/PCCH scheduling module allocates resources for common

channel transmission. The buffer size of common channels determines the TB Size
used in BCCH/CCCH/PCCH scheduling. The modulation coding mode is QPST, and
DCI1A and DCI1C are used to authorize common channels. The start positions of
RBs on the Broadcast Control Channels (BCCHs) between neighbor cells are
randomly distributed to reduce interference between cells.
If SPS is enabled, the SPS module manages the scheduling for VoIP services.
The retransmission module manages HARQ process retransmission. The downlink

HARQ uses adaptive retransmission. The start position of the RB in retransmission
must be the same as that in initial transmission. If no RB resource is available, the
module continues searching for the following RBs.
If a UE needs to transmit MAC Control Elements (CEs), the MAC CE scheduling

module determines the TB Size based on the size of the MAC CE packet, and further
determines the PRB according to the channel-quality-based MCS.
If a UE needs SRB transmission, the DCCH scheduling module calculates the sum
of buffer sizes of the UE SRB0, SRB1, and SRB2 to generate the TB Size, and
further determines the PRB according to the channel-quality-based MCS.
The QoS scheduling module generates a scheduling priority based on QoS

parameters to prioritize subscribers from different services for initial transmission. In
addition, the module determines the MCS and the number of PRBs for subscriber
scheduling through the AMC function.
The RB allocation module determines the PRB position based on different

frequency-domain resource allocation schemes.
The MAC statistics module collects the information of the MAC scheduler, and
reports the statistical result to the OAM module for KPI information collection.
3 Technical Description
3.1 Definitions
 CFI (Control Format Indicator)
Number of OFDM symbols occupied by a Physical Downlink Control Channel (PDCCH)

in a subframe. Options include 1, 2, 3 and 4. 4 is a reserved value.
 CCE
Basic unit of resources allocated to Downlink Control Information (DCI). The minimum
unit for LTE resource allocation is RE. In the symbols occupied by a PDCCH, four REs
constitute a REG. 36 REGs constitute a CCE. The CCE aggregation level refers to the
number of CCEs used as a group for control resource allocation. Options include 1, 2,
4 and 8.
 HARQ information
HARQ information contains a New Data Indicator (NDI) and the size of a
Transport Block (TB). For DL-SCH transport, HARQ information also includes
an HARQ process ID. For UL-SCH transport, HARQ information also includes
a redundancy version (RV). In DL-SCH spatial multiplexing, HARQ information
contains the NDI and the size of each TB.
 QCI
QoS Class Identifier which indicates the type of a service and the quality indexes for the
service. Service types include conversation, streaming, interaction, and background.
 QoS
Quality of Service which indicates the performance of packets or data flows when they
are transmitted through the network. This performance is described by a set of
measurable parameters. In an IP network, a data flow is described by four basic QoS
parameters: reliability, latency, jitter and bandwidth.
3.2 Technical Details
3.2.1 Logical Channels and Transport Channels
3.2.1.1 Logical Channels
The MAC layer provides data transmission services for RLC through logical
channels. Logical channels include control logical channels and service logical
channels. The control logical channels are used to transmit control data, for example,
Radio Resource Control (RRC) information. The service logical channels are used
to transmit user plane data.
1. Control Logical Channels
 Broadcast Control Channel (BCCH): downlink channel, used to broadcast system

information. In RLC, the channel is correlated with a TM RLC entity.
 Paging Control Channel (PCCH): downlink channel, used to notify UEs of an incoming call
or system information change.
 Common Control Channel (CCCH): used to transmit uplink or downlink control information,
for example, for link establishment, when an association is not established between the
eNodeB and a UE. In RLC, the channel is correlated with a TM RLC entity.
 Dedicated Control Channel (DCCH): used to transmit uplink or downlink control

information for a specified UE when the RRC link is established between the eNodeB
and a UE. In RLC, the channel is correlated with an AM RLC entity.
2. Service Logical Channels
Dedicated Traffic Channel (DTCH): used to transmit uplink or downlink data for specified
subscribers. In RLC, the channel is correlated with a UM RLC entity or an AM RLC
entity.
3.2.1.2 Transport Channels
1. Downlink Transport Channels
 Broadcast Channel (BCH)
 Downlink Shared Channel (DL-SCH): used to transmit subscriber data or control

messages. In addition, part of system information is transmitted through the channel.
 Paging Channel (PCH): used to transmit UE paging messages and notify UEs of system
information update.
2. Uplink Transport Channels
 Uplink Shared Channel (UL-SCH): used to transmit uplink subscriber data or control
information.
 Random Access Channel (RACH): used for network access when a UE has no uplink
synchronization or no uplink transmission resource. For the mapping between the uplink
transport channels and physical channels, refer to the reference document [2] in chapter
5.
3.2.1.3 Multiplexing and Mapping
The figures below show the multiplexing and mappings between downlink
logical/transport channels and uplink logical/transport channels.
Figure 3-1 Mapping Between Downlink Logical Channels and Downlink Transport
Channels
Figure 3-2 Mapping Between Uplink Logical Channels and Uplink Transport Channels
The DL-SCH transmits all logical channel data except the PCCH data. For enhanced
Multimedia Broadcast/Multicast Services (eMBMSs), the Multicast Traffic Channel
(MTCH) and Multicast Control Channel (MCCH) can be mapped to the DL-SCH or
Multicast Channel (MCH). This version does not support the MTCH or MCCH.
3.2.2 Scheduling Policies
3.2.2.1 RR
The RR algorithm guarantees that subscriber polling in cells is scheduled. The

scheduler prioritizes UEs based on wait time, and first allocates radio resources to
the UE that waits for the longest time for scheduling. The RR algorithm is not affected
by the radio channel quality. If the transient quality of a subscriber’s radio channel is
very poor with low traffic, the RR algorithm cannot improve the channel quality. The
algorithm only guarantees that each subscriber obtains an equal scheduling
opportunity within a specified time period.
The RR algorithm involves the following parameters:
1. Silence duration: Each subscriber shares an equal scheduling opportunity, and thus the
accumulated duration that each subscriber waits for scheduling is identical.
2. Probability theory: Each subscriber is scheduled by polling, and the scheduled

probability (p(k)) is 1/k (k indicates the number of subscribers that wait for scheduling).
Therefore, each subscriber occupies the equiprobable resources, for example, time,
power, and PRB.
The RR algorithm allocates an equal scheduling opportunity to each subscriber to
ensure that subscribers share the equiprobable scheduling in both short and long
time periods.
The RR algorithm is the scheduling algorithm to best guarantee subscriber

scheduling equity. However, the priority obtained from the algorithm does not
consider subscribers’ channel parameters (for example, SINR, CQI, and buffer
status), and thus system resources may be wasted, for example, low cell throughput
and cell frequency spectrum efficiency.
In the RR algorithm, the priority factor FF is described as follows:
The equation above shows that a longer waiting duration for scheduling results in a
higher scheduling priority.
3.2.2.2 MAX C/I
The MAX C/I algorithm is the scheduling algorithm that best indicates channel
conditions. The algorithm first schedules subscribers with the best channel quality
and ignores subscribers’ historical throughput. The algorithm makes the subscriber
obtain the highest system/cell throughput, but it results in inequitable resource
allocation and limited coverage range.
The MAX C/I algorithm prioritizes subscribers based on the subscribers’

instantaneous carrier-to-interference ratios. The priority factor is described as
follows:
TB(i) indicates the Transport Block Size (TBS) of stream i. As specified in 3GPP
36.213, the TBS is obtained from the UE-reported CQI mapping.
The MAX C/I algorithm determines subscribers’ scheduling priorities based on the
subscribers’ radio channel quality. Therefore, UEs with the best channel quality can
obtain the highest throughput, while edge UEs are difficult to be scheduled due to
poor carrier-to-interference ratios.
The algorithm is the most inequitable algorithm in terms of resource usage. Based
on this algorithm, however, subscribers with better channel quality can obtain higher
modulation modes, for example, 16QAM, 64QAM, and more transmission layers.
Compared with the RR algorithm, the MAX C/I algorithm guarantees a higher data
throughput with the same bandwidth.
3.2.2.3 PF
The Proportional Fairness (PF) algorithm is a compromised scheduling algorithm,

which guarantees the maximum throughput for the radio network, and an equal
scheduling opportunity for subscribers.
In the LTE system, the PF algorithm includes the following factors: UL/DL channel
quality, subscriber buffer update status, average scheduling duration per subscriber,
and QoS parameters.
Compared with the MAX C/I algorithm, the PF algorithm provides more equitable
scheduling. In addition to multi-subscribers’ diversified gains, the algorithm also
considers the influence of time difference due to SINR change in case of a single
subscriber with a fading channel. The algorithm can select proper time, proper
subscribers, and proper resources for data transmission.
The algorithm obtains the subscriber priority through the following equation:
For the TB(i) description, refer to that in the MAX C/I algorithm. The historical
throughput is calculated through the following equation:
is a filtering factor and ranges from 0.01 to 0.05. TBSIZE is the actually allocated
transport block size after scheduling at the previous TTI. If the UE is not scheduled
at the previous TTI, equation (1) of the historical throughput is used. If the UE is
scheduled at the previous TTI, equation (2) is used.
The PF algorithm is an equitable scheduling algorithm because it guarantees that

subscribers camping on a cell can be scheduled at the same bit rate. In addition, the
PF algorithm also guarantees that the scheduled subscribers with better channel
quality obtain higher system throughput. The PF algorithm is also a combined
algorithm of the MAX C/I and Equal Bit Rate algorithms.
3.2.2.4 ER
The Equal Rate (ER) algorithm guarantees that all subscribers obtain a roughly
identical bit rate.
The ER algorithm obtains the subscriber priority through the following equation:
For the historical throughput description, refer to that in the PF algorithm.
3.2.3 HARQ
3.2.3.1 Synchronous HARQ and Asynchronous HARQ
Synchronous HARQ predefines the retransmission time and the relative time of initial
transmission for each HARQ process. In this mode, the HARQ process ID can be
calculated based on a transport timeslot instead of being obtained from a signaling
message.
The uplink HARQ of Frequency Division Duplex (FDD) is synchronous. The eNodeB
receives data on subframe n, and sends an ACK or NACK message to a UE on
subframe n+4. The UE then transmits or retransmits the data on subframe n+8.
Therefore, data is transmitted or retransmitted on the fixed subframes in the
synchronous HARQ process. In the asynchronous HARQ process, data can be
retransmitted at any time relative to the initial transmission, and thus extra signaling
is required to indicate the HARQ process ID so that the receiver can properly obtain
the initial transmission associated with the retransmission. In short, synchronous
HARQ decreases signaling overhead, while the asynchronous HARQ has more
flexible scheduling.
The downlink HARQ of FDD is asynchronous. The eNodeB sends data on subframe
n, and the UE sends an ACK or NACK message on subframe n+4. The eNodeB
transmits or retransmits the data on any subframe following subframe n+4.
3.2.3.2 Adaptive and Non-adaptive HARQ
In adaptive transmission, transmission attributes, for example, modulation coding

mode and frequency-domain transmission resources, vary with different radio
channel states. Therefore, an explicit PDCCH indication is required for
retransmission authorization.
Non-adaptive retransmission has no explicit signaling to indicate transmission

attributes, and uses the same transmission attributes as those in initial transmission
or changes the attributes according to the predefined policies. The adaptive
retransmission creates more scheduling gains by adding signaling overheads. The
non-adaptive retransmission does not require an explicit PDCCH indication for
retransmission authorization, and notifies an UE of using the same MCS and PRB
for retransmission by sending an NACK message to the UE through the Physical
Hybrid ARQ Indicator Channel (PHICH).
In the LTE system, adaptive asynchronous HARQ is used for downlink transmission,
and synchronous HARQ is used for uplink transmission. For the uplink transmission,
either adaptive retransmission or non-adaptive retransmission can be used based
on the transmission attributes indicated in a signaling message.
3.2.3.3 HARQ Retransmission Modes
If any error occurs in initial transmission, HARQ retransmits the erroneous packets.
In the current ZTE solution, the original BLER target for the inner AMC is 10%. The
BLER targets may vary with different services. To guarantee the remaining BLER
targets, the times of HARQ retransmissions vary with different services.
HARQ retransmission for error compensation includes CC and IR modes.
In CC mode, the same packet that was initially transmitted is retransmitted as a

whole. The receiver combines the retransmitted packets and buffer data in initial
transmission according to the predefined policies to promote decoding reliability and
fulfill the performance gains of the entire system. The combination of two same
packets enhances the effect of redundant coding, and thus a 3 db gain can be
obtained.
In IR mode, the packets that consist of information bits and parity check bits of
different parts are transmitted during retransmission. The code blocks initially
transmitted are combined with the retransmitted code blocks during decoding. The
receiver uses the code block of the corresponding part based on the transmission
times to obtain more information of the entire code blocks. Compared with the CC
mode, the IR mode is more diversified but has a time limit.
3.2.3.3.1 Downlink HARQ
There are up to eight HARQ processes for downlink transmission, and the UE sends
a PDSCH ACK or NACK message.
If the ACK or NACK message cannot be repeatedly transmitted, the UE detects the
PDSCH on subframe n-4, and returns an ACK or NACK message on subframe n.
Downlink retransmission uses adaptive asynchronous HARQ, which indicates that

the HARQ process ID is sent to the UE and resource allocation in the frequency
domain changes. MCS29-31 can be used to adjust the modulation and demodulation
modes of downlink transmission. The TB size must be the same as that in the
previous transmission.
If UL-SCH data needs to be transmitted, an ACK or NACK message is sent on the

PUSCH. Otherwise, the ACK or NACK message is sent on the PUCCH.
The PDCCH indicates the HARQ process ID for initial transmission and
retransmission.
Retransmission is scheduled on the PDCCH.
3.2.3.3.2 Uplink HARQ
Uplink transmission has up to eight HARQ processes for non-subframe binding and
up to four HARQ processes for subframe binding. Subframe binding is configured by
a higher layer through the swchTTIBundling parameter.
Subframe binding is only applicable to the UL-SCH, and is used on four consecutive
uplink subframes.
For the common HARQ operation, if a UE detects PDCCH or PHICH carrying DCI0
on subframe n, it adjusts PUSCH data transmission on subframe n+4 based on the
PDCCH and PHICH.
For subframe binding, if the UE detects PDCCH carrying DCI0 on subframe n or

detects PHICH on subframe n-5, it adjusts PUSCH data transmission on subframe
n+4 based on the PDCCH and PHICH.
Uplink retransmission uses adaptive or non-adaptive synchronous HARQ. If only

receiving an NACK message but not DCI0, the UE retransmits the data using the
same MCS and PRB as those in the previous transmission. If receiving DCI0, the
UE retransmits data according to the new authorization adjustment information.
During adaptive uplink retransmission, the TB size must be the same as that in the
previous transmission. MCS29-31 is used to indicate different RVs.
3.2.3.4 Key Parameters
The following four HARQ parameters are important for ZTE eNodeBs although these
parameters are un-modifiable.
 Uplink HARQ mode: CC, non-self-adaptive IR, or self-adaptive IR.
 Downlink HARQ mode: CC or self-adaptive IR.
 The number of HARQ processes depends on the round-trip delay of the UE. More HARQ
processes require more memories reserved for the UE.
 The maximum number of HARQ processes depends on the round-trip delay of the UE
and the required BLER of the service. More HARQ processes mean longer delay and
larger BLER
3.2.4 QoS
Quality of Service (QoS) can be measured by a number of parameters, such as QCI,

GBR, AMBR, Packet Delay Budget (PDB), and Packet Error Rate (PER). ZTE LTE
supports QoS-based scheduling to ensure QoS on the bearer layer, meaning
supporting the scheduling priority of each bearer of multi-bearer users. The QCI-
based QoS scheduler of the ZTE eNodeB can calculate the scheduling priority of
each uplink or downlink bearer.
3.2.4.1 Priority Queue
The QCI-based QoS scheduler of ZTE eNodeB processes the priorities of all uplink
and downlink bearers. This version supports the following priority management:
1. The ZTE scheduler defines the MAC Logical Channel Priority (MLP). For multi-bearer
users, the scheduler uses the RRM algorithm to calculate the MLP according to the QCI,
which, in the current version, is indicated by the RRC layer to the MAC scheduler. An
MLP scheduling queue consists of one or multiple logical channels that have the same
MLP. In the current version, only the absolute QCI scheduling priority is considered. In
later versions, operators can configure the absolute or related QCI priority.
2. The scheduling policy can be configured to Round Robin (RR), Proportional Fair (PF) or
MAX C/I.
3. The UL QoS scheduler is based on the Logical Channel Group (LCG). Different from the
DL QoS scheduler, which is based on the logical channel, the LCG MLP depends on
the highest-priority logical channel in the LCG. The GBR and MBR of the LCG are
defined respectively as the total GBRs and MBRs of all logical channels in the LCG.
4. For the calculation of the logical channel priority in an MLP queue, the FF is used to help
with priority queuing. If the scheduling policy is configured to RR, the FF is used. If the
scheduling policy is configured to MAX C/I, the MAX C/I is used. If the scheduling policy
is configured to PF, the following algorithm is used. The FF in the PF scheduling policy
consists of three FFs: FFPF, FFQoS, and FFAMBR. Same as ordinary PF scheduling
scheme, FFPF represents a fair factor and radio channel condition and maximal history
throughput are considered; the factor FFQoS gives consideration to the QoS property of
the bearer. In the current version, consideration is only given to FFGBR, which is based
on the GBR value and historical success data rate. In later versions, FFDELAY, which is
based on PDB and time packet waiting time in the buffer area, will be considered. If the
UE supports the AMBR service, the fair factors of the QoS scheduler are as described
in the following figure.
Figure 3-3 FFs in the Qos SchedulerQos
5. The current version supports ARP-based absolute and relative user scheduling priority
in the MLP of the PF scheduling policy. If this function is enabled (this version does not
allow the operator to configure the priority, but the later version will do), the user-priority
fair factor FFarp is especially considered in calculating logical channel FF of one MLP
queue, where FFarp can be configured. Gold users have the highest priority, silver users
have lower priority, and bronze users have the lowest priority. The priorities of users are
mapped according to ARP levels.
 ARP level of gold users: 1 – 5;

 ARP level of silver users: 6-10;
 ARP level of bronze users: 11- 15
In an MLP queue, the relative scheduling priority of gold users is higher than silver users
and bronze users, that is, FFarp is not the conclusive factor for comparing the FF
algorithm and PF algorithm.
6. The figure below shows an example that an operator can configure the QoS scheduler.
There are nine MLP queues, and the QCIs of all logical channels in one MLP are the
same. The MLP priority depends on its QCI priority, which means that the queue whose
SRB&QCI is 5 has the highest priority, and the queue whose QCI is 9 has the lowest
priority. For the MLP of QCI 1 and NGBR, the scheduling policy can be configured by
the operator. For other GBR services, for SRB and QCI = 5, it is recommended to use
the RR algorithm. For the queue whose SRB&QCI is 5, gold users have the highest
priority, and silver users and bronze users are configured with absolute priority. After
being scheduled, all the successfully scheduled logical channels of one UE need to be
combined as shown in the figure below (UE1 as an example).
Figure 3-4 Operator-Configurable QoS Scheduler
3.2.4.2 Priority Bit Rate
The priority bit rate is used for MAC priority queuing and resource estimation.
For uplink traffic, the protocol specifies that the PBR is used for UE group PDUs (The eNodeB
performs resource authorization according to the UE).
For downlink traffic, the PBR is the minimum guaranteed rate allocated to each NGBR bearer
by the eNodeB. The downlink PBR is a non-protocol field.
 The PBR configuration is related to the services mapped on a QCI by the operator.
If the PBR is set too high, the NGBR occupies a large number of PRBs and
overload the cell. If the PBR is set too low, user experience is poor. An appropriate
minimum guaranteed rate should be configured depending on services.
Pseudo GBR for NGBR is based on QoS, and it is an optimization and supplement
for QoS function.
3.2.4.3 MBR > GBR in R10
This feature supports the MBR > GBR feature defined in 3GPP R10. With this feature
enabled, if the cell load is low, the GBR service can be excessively used within the
range of the configured MBR. In this case, users can enjoy the High Definition (HD)
GBR service. If the cell load is high, the GBR service operates at the GBR rate and
users are provided with only Standard Definition (SD) or just smooth GBR service.
3.2.4.4 Dynamic Scheduling
3.2.4.4.1 Uplink Dynamic Scheduling
The figure below shows the uplink dynamic scheduling flow. The scheduling flow is
as follows:
1. Goes through the MLP matrix, and checks whether there is a user that waits for
scheduling. If yes, go to step 2; otherwise, go to step 20.
2. Finds the user with the maximum FF value in the MLP matrix.
3. Checks whether the bearer established for the user in the MLP matrix is a GBR bearer.
If yes, go to step 4; otherwise, go to step 11.
4. Checks whether there is any GBR service limited by GBR parameters. If yes, go to step
5; otherwise, go to step 18.
5. Checks whether the CCEs are allocated. If yes, go to step 7; otherwise, go to step 6.
6. Checks whether there are any idle PDCCH CCEs at the current TTI. If yes, the CCEs
are allocated to the subscriber, and go to step 7; otherwise, go to step 18.
7. Calculates the minimum number of PRBs that the subscriber needs in the MLP
matrix, and estimates the frequency spectrum efficiency according to authorized BSRs
and GBRs of the UE and the SINR reported through the SRS or PUCCH DMRS.
8. Checks whether the ICIC function is enabled, and checks whether the subscriber is a
cell edge subscriber. If yes, go to step 9; otherwise, go to step 10.
9. Compares the with the number of the remaining edge PRBs, updates the
number of needed RBs according to , and then updates

the remaining authorized scheduling for the GBR service.
10. Compares the with the number of the remaining RBs in the cell, updates
the number of needed RBs through , and then updates

11. For an NGBR service, checks whether there is any authorized NGBR service limited by
AMBR parameters. If yes, go to step 12; otherwise, go to step 18.
12. Checks whether the CCEs are allocated to the user. If yes, go to step 14; if not, go to
step 13.
13. Checks whether there are any idle PDCCH CCEs at the current TTI. If yes, the CCEs
are allocated to the user, and go to step 7; otherwise, go to step 18.
14. Calculates the minimum number of PRBs that the subscriber needs in the MLP
matrix, and estimates the frequency spectrum efficiency according to authorized BSRs
and GBRs of the UE and the SINR reported through the SRS or PUCCH DMRS.
15. Checks whether the ICIC function is enabled, and checks whether the subscriber is a
cell edge subscriber. If yes, go to step 16; otherwise, go to step 17.


the remaining authorized scheduling for the NGBR service.
18. Deletes the subscriber from the MLP matrix.
19. Updates the number of remaining available CCEs, CCE positions, and the number of
RBs. Return to step 1.
20. Skips to the next column of the MLP matrix, and finds the next available MLP queue to
be scheduled.
21. Checks whether the current queue is the last queue in the MLP matrix. If yes, return to
step 1; if not, go to step 22.
22. Merges all the RBs allocated to the subscriber in different MLP queues upon the
completion of uplink scheduling at the current TTI.
Figure 3-5 Uplink Dynamic Scheduling Flow
 BSR Reporting
The BSR provides the serving eNodeB with the data size that a UE can transmit in
the uplink buffer.
There are two timers to control BSR reporting: periodic BSR timer and
retransmission BSR timer. The eNodeB specifies the timer type through an RRC
message.
 MCS and RB Allocation
After the number of RBs is calculated, the MCS can be determined according to the
link statuses described, and the RB position can also be determined according to
the FSS or NFSS-based frequency-domain scheduling module described.
3.2.4.4.2 Downlink Dynamic Scheduling
The downlink dynamic scheduling policies are similar to the uplink dynamic
scheduling policies. The differences are as follows:
Only up to four MLPs are provided for the UL DTCH, because 3GPP defines only
four LCGs and UL scheduling is based on the LCG. Up to 15 MLPs are provided for
the DL DTCH, which indicates that there are multiple DTCHs in an MLP queue of a
UE at a TTI. Therefore, the DL scheduler needs to search for the remaining DTCHs
that wait for scheduling in the MLP queue after one DTCH is scheduled.
DL MIMO transmission provides open-loop and closed-loop spatial multiplexing. The

UL supports single-flow transmission, while the DL supports single-flow or dual-flow
transmission. Therefore, the minimum number of PRBs needed by one DTCH

in an MLP queue of a UE is calculated based on the UE-reported BSR, the remaining
authorized GBRs or NGBRs, and the estimated frequency spectrum efficiency
according to the QCI of the UE-reported single flow or dual flows.
 Number of Transmission Layers
The UE-reported RI value is considered when the number of transmission layers is

determined. To simplify retransmission, the actually used number of transmission
layers is higher or lower than the reported RI. The detailed descriptions, the chapter
of adaptive downlink MIMO policies is described.
 MCS and RB Position
After the number of RBs is calculated, the adaptive link module determines the MCS.
The FSS or NFSS-based frequency-domain scheduling module determines the RB
position.
 AMBR Traffic Control

Aggregate Maximum Bit Rate (AMBR) refers to the maximum traffic of all NGBR
bearers per UE. The uplink and downlink AMBR traffic control mechanisms are the
same. On the MAC layer, the uplink and downlink historical traffic of each UE is
recorded. If the total traffic exceeds the AMBR of the UE, the services of the UE are
not scheduled. The AMBR includes user-plane data retransmission except for MAC
data retransmission. The time windows for uplink and downlink AMBR traffic control
are both 50ms.
To avoid low throughput upon arrival of burst uplink data, during the uplink link
scheduling, the MAC layer calculates the accumulated TB Size after the ERAB is
established. The calculation lasts for up to one second or stops when the uplink data
arrives. The accumulated TB Size may be 2 * AMBR.
 MIMO Transmission Solutions' Impact on Scheduling
The MIMO transmission solutions affect the scheduling result. The common
transmission modes include:
 TM2: transmit diversity
 TM3: Dual-layer open-loop spatial multiplexing
 TM4: single or dual-layer closed-loop spatial multiplexing
The transmission solution for a subscriber is determined by the radio link conditions
and cell-level MIMO configuration. For details, refer to section 3.2.7. The
transmission solutions also affect radio resource allocation. Under the same radio
link condition, radio resource allocations vary with different transmission solutions.
For example, based on the Max C/I algorithm, a higher TB Size can be scheduled to
the UE with RI being 2, and the scheduling probability of this UE is higher than that
of the UE with RI being 1 under the same radio link condition (with the proximately
same SINR).
For the precoding policy of the MIMO transmission solution, refer to the description
of the LTE FDD physical-layer functions.
3.2.4.5 PDCCH and CFI Allocation
1. DCI format
DCI 0 is used for uplink scheduling authorization. DCI 1 is used for a single-
antenna transmission solution. DCI 1A is used in common channels (for
example, BCCH/PCCH) and for signaling control (for example, random access
response). In addition, DCI 1A is also used for adaptive transmit diversity in TM3
mode. DCI 2 is used for closed-loop spatial multiplexing. DCI 2A is used for
open-loop spatial multiplexing.
2. CCE aggregation
The CCE aggregation level is adaptive to radio link conditions. In this version,
the CCE aggregation parameters can be configured by operators. In BPL0, the
aggregationUl and aggregationDl parameters respectively indicate the uplink
and downlink CCE aggregation levels, and can be configured to 1, 2, 4, 8, or
dynamic. For example, if the aggregationUl or aggregationDl parameter is set
to dynamic, the uplink or downlink CCE aggregation level and the corresponding
PDCCH power offset are dynamically adaptive. In BPL1, the cceAdaptMod
parameter indicates the UL or DL CCE aggregation level, and can be configured
to 1, 2, 4, 8, or adaptive. For example, if the cceAdaptMod parameter is set to
adaptive, the UL or DL CCE aggregation level and the corresponding PDCCH
power offset are dynamically adaptive.
Figure 3-6 Adaptive PDCCH Flow
The adaptation of the PDCCH CCE aggregation level and the power offset are based
on the PDCCH BLER. The BLER is calculated according to PDCCH, PDSCH DTX,
and PUSCH Miss as follows:
 If the PDSCH DTX and PUSCH Miss are lower than the preset thresholods, either
the CCE aggregation level or the power offset decreases. If the CCE allocation
fails, other CCE aggregation levels and power offsets are attempted. For example,
to guarantee a lower BLER in the case of the decrease of the CCE aggregation
level, the PDCCH power offset is increased. The CCE resources are reallocated
until the CCE allocation succeeds or no resource is available.
 If the PDSCH DTX and PUSCH Miss are higher than the preset thresholods, the
CCE aggregation level and power offset increase.
3. CFI
This version supports the adaptive and configurable CFI. Operators can configure the
CFI parameter to 1, 2, 3, or dynamic. If the parameter is set to dynamic, the CFI is
determined by the system bandwidth, historical CCE needs, and historical CCE
allocation. Figure 3-9 shows the adaptive CFI flow.
Figure 3-7 Adaptive CFI Flow

3.2.4.6 TCP RTT Optimization
eNodeB estimates the TCP packet size according to the downlink scheduled TCP
packets and forms the BSR at the corresponding scheduled time (mainly considering
the fact that UE may accumulate feedback packets, which results in BSR
accumulation and excessive padding). The UE with virtual Buffer Status Report
(BSR) is called pre-scheduled UE. The pre-scheduled UE and dynamic UE are
scheduled with PF algorithm. The pre-scheduling time should be pre-estimated
according to TCP_ACK time reported by UE, and pre-scheduling starting moment
and duration time can be adjusted through parameters. This feature is enabled by
default.
The size of BSR is estimated according to the following principle:
Size of BSR= (TCP_ACK packets at UE side/2) *40Byte
Of which,
1. On UE side, two TCK-ACKs are packaged together to feedback usually;
2. 40B is unit of feedback packets. The value corresponds to TCP header + IP

header (IPV4). Here 40B is the minimum value of TCP_ACK packet.
Figure 3-8 TCP RTT Optimization

3.2.5 Link Adaptation
Adaptive Modulation Control (AMC) is a key technology of dynamic scheduling. After

the number of RBs is determined, the MCS is determined in the inner-loop AMC and
tuned according to radio channel quality in the outer-loop AMC. ZTE AMC supports
inner-loop and outer-loop AMC, see the following figure.
Figure 3-9 AMC Function
The AMC has the following advantages:

 Corrects UE measurement errors.
 Corrects the CQI offsets reported by different UEs.
Performs outer-loop adaptive AMC based on actual environments.
3.2.5.1 Downlink Adaptation
A UE reports downlink CQI values periodically or according to a request. The MAC

scheduler determines the MCS for the downlink data transmitted to the UE based on
the broadband CQI. The system performance indexes, for example, BLER, are
counted within the specified period. If the BLER is higher than the preset threshold,
the MCS value decreases. If the BLER is lower than the other preset threshold, the
MCS value increases.
Figure 3-10 Downlink Adaptation Flow
 Key Parameter
CQIExpiredTimer: inner-loop CQIExpiredTimer is set to be 1280ms by default. The timer is

used to guarantee the inner-loop validity. If CQI reported by UE is received by the downlink
when the timer is running, it is regarded as inner-loop valid; If CQI reported by UE is not
received by the downlink when the timer is running, it is regarded as inner-loop invalid and
the downlink enters into conservative scheduling.
3.2.5.2 Uplink Adaptation
The eNodeB obtains an SINR by measuring the SRS and PUSCH DMRS. The MAC
layer at the eNodeB side determines the MCS for UE scheduling based on the
broadband SINR and the UE-reported PHR. If the UE power is limited, the measured
SINR is averaged according to the PHR, and the RB is allocated based on the
method described in section 3.2.4.2.1. Similar to downlink adaptation, the eNodeB
maintains the BLER by counting the performance indexes and performing filtering,
and use the BLER to control the MCS. If the BLER is higher than the preset
threshold, the MCS value decreases. If the BLER is lower than the other preset
threshold, the MCS value increases.
Figure 3-11 Uplink Adaptation Flow
3.2.5.3 Small Packets Service Optimization
If the number of RBs is not more than 16, the sub-band SINR meeting the timeliness
requirement or the SINR of the occupied RB meeting the timeliness requirement
should be used to obtain the SINRRB after an equivalent calculation.
If the sub-band SINR or the SINR of the occupied RB is ineffective, the SINRRB is
calculated based on the broadband SINR; that is, SINRRB = SINRbroadband.
The MCS is re-mapped based on the SINRRB. MCS mapping is related to whether
the power is restricted or not.
If the power is not restricted, the MCS can be obtained from the SINR-MCS mapping
table.
If the power is restricted, the system recalculates SingleRBSINR based on the

conservatively-calculated SINRRB. With the SingleRBSINR and the number of RBs,
the system obtains the MCS by querying the SingleRB_SINR configuration table. If
the high-stability feature is enabled, the MCS is restricted by the upper limit of the
virtual MCS. If the number of RBs is not found in the SingleRB_SINR configuration
table, the MCS is calculated as follows:
The difference (SINRΔ) between the SINRRB and the SINRbroadband can be converted into
ΔMCS.
ΔMCS = α × SINRΔ, where α indicates a conversion factor and 0.66 is used.
The currently-used MCS can be adjusted and protected against overrun based on ΔMCS.
3.2.6 Self-Adaptive Downlink MIMO Mode
3.2.6.1 Ordinary Downlink MIMO Mode
In the current version, the general downlink transmission modes are as follows:
 TM1: single antenna;
 TM2: Transmit diversity;
 TM3: open-loop spatial multiplexing;
 TM7: Beam-forming;
 TM8: dual-stream beam-forming;
These MIMO modes are used in the following scenarios:

 Single antenna: single-antenna scenarios;
 TX diversity: provide diversity gains in fading scenario;
 Open-loop spatial multiplexing: used for medium- and high-mobility environment for better
spectrum efficiency
 Beam-forming: Adjust weight of each element of the antenna matrix, and antenna beams
point to the UE all the time.
3.2.6.2 Self-Adaptive Downlink MIMO Mode
In the current version, the following two factors affect the downlink MIMO self-
adaptive:
 Changes of channel correlation corresponding to rank indication
 Changes of the UE’s radio environment and location
3.2.6.2.1 Effect of Correlation Environment
1. Low-correlation environment
In low-correlation environments, that is, RI> 2, the following downlink transmission

modes can be used:
 Open-loop spatial multiplexing
 Dual-layer BF (for 3GPP R9 or later)

2. High-correlation environment
In high-correlation environments, that is, RI=1, the following DL transmission modes can
be used:
 TX diversity (transmit diversity)
 Single-stream BF, including Port5 (TM 7), Port7 or Port8 (TM8).

3. Self-adaptive handover based on channel correlation change
 If the handover is from a low-correlation environment to a high-correlation

environment, TX diversity or single-stream BF is used.
 If the handover is from a high-correlation environment to a low-correlation

environment, open-loop spatial multiplexing or dual-stream BF is used
3.2.6.2.2 Effect of Location Changes

1. Cell center or good radio channel environment
In the cell center or a good radio environment, where the SINR is good, the following
downlink multi-antenna transmission mode can be used:
 Open-loop spatial multiplexing

2. Cell edge or poor radio environment
In the cell edge or a poor radio environment, where the SINR is poor, the following
downlink transmission modes can be used on condition that the rank indication is
greater than 1 at the same time.
 TX diversity (transmit diversity)
 Single-stream BF, including Port5 (TM 7), Port7 or Port8 (TM8).

3. Single-stream BF, including Port5 (TM7), Port7 or Port8 (TM8), location or radio
environment self-adaptive
 If UE is moving for cell center to cell edge, or SINR is less than a threshold, single-
stream scheduling will be adopted like transmit diversity or single-stream
beamforming.
3.2.6.2.3 Downlink MIMO Mode Selection

1. Configuration at the Initial Access
The downlink multi-antenna transmission mode of the UE can be configured at the

following two time points during the initial access:
 After an RRC connection is established
 After the UE capability level is acquired
For the configuration principle of the downlink multi-antenna transmission mode, see
the following figure:
Figure 3-12 Configuration Principle of Downlink Multi-Antenna Transmission Mode at the

Initial Access
(1) After an RRC connection is established

1) If the eNodeB is configured with only a single-antenna port, the downlink
transmission mode is configured to TM1 by default.
2) Otherwise, the downlink transmission mode is configured to TM2 by default
(2) After the UE capability level is acquired
1) If the eNodeB is configured with only a single-antenna port, the downlink
transmission mode is also configured to TM1. Reconfiguration is not
needed;
2) Otherwise, the eNodeB check the UE capability. If the UE capability level is
1, the downlink transmission mode is also configured to TM2. If the UE
capacity level is higher than 1, the downlink transmission mode is
reconfigured to TM3 by using a radio resource connection.
2. Self-adaptive Transmission mode after UE access
The current version supports self-adaptive in TM3, TM7, and TM8 modes, between TM3
and TM7 modes, or between TM3 and TM8 modes.
 Self-adaptive in TM3 mode
Either open-loop spatial multiplexing or TX diversity is selected. If the SNR is low

or the RI is 1, the transmission mode becomes TX diversity. If the RI is 2 or the
SNR increases, the transmission mode becomes open-loop spatial multiplexing.
Either single-stream BF or TX diversity is selected. If the SNR is high, TX

diversity is used. If the SNR is low and if single-stream BF has forming gains
while TX diversity does not, single-stream BF is used. Otherwise, TX diversity is
used.
Dual-stream BF, single-stream BF or TX diversity is selected. One of these three

transmission modes is selected for data transmission according to the current
channel quality and BF forming gain.
 Self-adaptive between TM3 and TM7 modes
If the SNR is high, the transmission is self-adaptive in TM3 mode. When the SNR
is low, and if the channel RI is 1, and if single-stream BF has forming gains, the
transmission is self-adaptive in TM7 mode.
 Self-adaptive between TM3 and TM8 modes
If the SNR is high, the transmission is self-adaptive in TM3 mode. If the SNR is
low, the current channel correlation is low, and if dual-stream BF has forming
gains while open-loop spatial multiplexing does not, the transmission is self-
adaptive in TM8 mode. If the channel correlation is high and single-stream BF
has gains while Space Frequency Block Code (SFBC) does not, the transmission
is also self-adaptive in TM8 mode.
3.2.6.2.4 Key Parameters
In the current version, inter-mode self-adaptive is configured by default. The number

of downlink antennas is configured to 4 or 8, and the number of ports is equal to or
greater than 2. If the UE supports the R8 protocol at most, the self-adaptive
procedure between TM3 and TM7 modes is used. If the UE support the R9 protocol,
the self-adaptive procedure between TM3 and TM8 is used.
3.2.7 Frequency Domain Scheduling
In this version, the uplink and downlink LTE schedulers support frequency selective
scheduling and non-frequency selective scheduling. Subscribers are first scheduled
and prioritized in the time domain according to the configured scheduling scheme,
and radio resources are allocated to the subscribers at the queue header in FFS or
NFFS mode.
3.2.7.1 Frequency Selective Scheduling
3.2.7.1.1 Uplink Frequency Selective Scheduling
In the uplink, the UE periodically sends SRSs. After multiple periods, the eNodeB
can acquire the SRS measurement values of all bandwidths and learn the signal
quality of different sub-bands. In a scheduling procedure, the eNodeB selects the
RB with good channel quality to transmit uplink services and obtain frequency gains.
It should be noted that whether to enable the frequency selection algorithm can be
configured at the EMS. After the frequency selection algorithm is enabled, the RB
position allocation policy is to perform frequency selection-based allocation first.
When the number of RBs to be scheduled is less than or equal to 16, frequency
selection scheduling is used. Otherwise, bandwidth scheduling is used.
3.2.7.1.2 Downlink Frequency Selective Scheduling
Downlink frequency selection scheduling is based on the sub-band CQI reported by

the UE. The principle is described as follows: When downlink frequency selection
scheduling is enabled, the UE can select a sub-band to report CQIs or the upper-
layer can configure a sub-band to report CQIs. The sub-band CQIs reported by the
UE are different in the entire system bandwidth and different CQIs represents
different channel quality. Therefore, by maintaining the UE-level sub-band CQI
queue, the eNodeB traverses the CQI queue and allocate the RB location with good
channel quality to the UE first.
The sub-band CQI is time-sensitive. In downlink frequency selection scheduling,
when the best sub-band is selected, the time-insensitive sub-bands are not
considered. If there is no time-sensitive sub-band in the sub-band CQI queue,
bandwidth scheduling is used.
If the RB obtained by the RB calculating module is less than 1/4 of the system
bandwidth, frequency selection scheduling is not used.
3.2.7.2 Non-Frequency Selective Scheduling
The channel quality information of specific frequencies is unavailable in some

circumstances, for example, when a UE is moving at a high speed in the environment
of high Doppler frequency shift, or VoIP with low traffic. Non-frequency selective
scheduling can eliminate fast fading in the low-network-load environment and
randomized inter-cell interference by using the frequency diversity of LTE broadband
channels.
In this version, the non-frequency selective scheduling solution in the scheduler uses
broadband allocation. In the solution, the RBs allocated to subscribers are selected
from idle RBs beginning with the system low-frequency, or the static ICIC is
configured when the ICIC function is enabled. The allocated RBs through the uplink
CMAC must be idle and consecutive from the starting position of RBs, while the
allocated RBs can be inconsecutive in the downlink direction.
If the PF scheduling policy is used, a subscriber can obtain randomized frequency

diversity gains at different TTIs. The randomized frequency diversity gains depend
on random queue priority in the time domain.
3.2.7.2.1 Downlink PRB Random Allocation
In broadband non-frequency selective allocation under medium and low loads,

downlink interference exists between neighbor cells because all cells allocate
downlink PRBs from the same starting position of the system bandwidth. To
eliminate the interference, ZTE develops random PRB allocation in frequency-
domain scheduling. In the scheduling, each cell allocates PRBs in random order by
using a unique random PRB bitmap.
If the freqSelectDl parameter is set to downlink randomized PRB allocation, the

downlink CMAC enables the PRB randomization function. The randomized downlink
PRB allocation flow is as follows:
Step 1: The cell generates a random integer N (N = RAND+PCI).

Step 2: Determines the RB starting position of the cell according to mode (N, 3).
Mod (N, 3) = 0: The RB starting position is 0.
Mod (N, 3) = 1: RB starting position = floor ((rand% (K-L)/RBG size)), that

is, generates a random integer between 0 and K-L ([0,K-L]), and aligns with the
starting RB index of the RBG. K indicates the total number of available RBs of the
cell bandwidth when the number of RBs is allocated at the current TTI. L indicates
the total number of RBs allocated to all subscribers in the cell when the number of
RBs is allocated at the current TTI.
Mod (N, 3) = 2: The RB starting position is the RB position of the maximum

bandwidth in the cell.
Step 3: Allocates the RB position.
Mod (N, 3) = 2: Allocates RB positions to subscribers in the cell in

descending order of frequencies. For other values, RB positions are allocated to
subscribers in ascending order of frequencies.
3.2.7.2.2 Uplink PRB Random Allocation
In broadband non-frequency selection mode in medium and low loads, all cells
allocate uplink PRBs at the same initial position of the system bandwidth. Therefore,
uplink interference exists between the neighbor cells. To deal with the interference,
ZTE has developed random PRB allocation in frequency domain scheduling.
Different cells use different PRB bitmap to allocate PRBs at random.
If the uplink frequency selection parameter freqSelectUl is set to uplink PRB random
allocation[6], the uplink CMAC enables PRB randomization. The principle of the
uplink PRB random allocation is described as follows:
Step 1: Plan the cell as a type A, B, or C cell by PCI.
 Type A cell: Start allocation from the lowest RB.
 Type B cell: Start allocation from 1/3 RB of the bandwidth.
 Type C cell: Start allocation from the highest RB.
Step 2: Determine which type the local cell belongs to according to the relevant calculation
rules, and calculate the initial PRB position of the cell.
Step 3: Allocate RBs from the initial PRB position.

3.2.7.3 NI Based Interference Avoidance Scheduling
The high-NI frequency bands can be determined based on the PUSCH channel NI
measured by the eNodeB. During scheduling, the high-NI areas can be avoided.
Note: This operation is applicable to the available RBs on the PUSCH.
The RB segment with high interference is determined every 100 ms as follows:
1. The eNodeB calculates the average NI filtering power ( , in dBm) of the available RBs
on the PUSCH (see note 1).
2. The eNodeB calculates the difference ΔNI (in dB) between the NI filtering power of each
available RB and the .

3. If ΔNI of an RB is over the preset threshold ΔNIthreshold (5 dB, for example) and the NI
value of the RB is more than the threshold NIthreshold (-98.5dBm, for example), the RB is
screened out. In this case, the corresponding position on the bitmap is set to 1 during
scheduling, indicating that the RB is unavailable due to high interference. Otherwise,
the RB is not screened out and the corresponding position on the bitmap is set to 0
during scheduling, indicating that the RB is available.
Note 1:
For a single UE, the following comment is added to the RBs available on the PUSCH
because the PUSCH occupies the resources of the PUCCH:
if (single UE and PUCCH blanking disabled) – see note 2
Determine high-interference NI over the full bandwidth

else
Determine high-interference NI for the RBs reserved for the PUSCH - see note 3
End
Note 2:
For a single UE, if PUCCH blanking is enabled, the available RBs on the PUSCH
are reserved for the PUSCH. If the algorithm is optimized later (for example, the
available RBs for a single UE indicate all RB resources excluding PUCCH blanking
resources), the set of RBs with high-interference for a single UE should be updated
to all RB resources excluding PUCCH blanking resources.
Note 3:
The RBs reserved for the PUSCH indicate all RB resources excluding the PUCCH-
occupied RBs calculated based on the CFI value.
During RB allocation, the number of available RBs should exclude the RBs occupied
by the high-interference RB segments. In addition, the location of available RBs
should avoid the areas with high interference.
During re-transmission, if part of or all destinations are determined as the locations

with high-interference RBs, the available RB segments are selected for re-
transmission (self-adaptive re-transmission).
SPS cannot be activated in a high-interference RB segment. After SPS activation, if

part of or all RBs allocated to SPS are determined as high-interference RBs, SPS
needs to be re-activated.
Like normal re-transmission, TTI bundling re-transmission should avoid the areas
with high-interference RBs. If part of or all destinations are determined as the
locations with high-interference RBs, the available RB segments are selected for re-
transmission (self-adaptive re-transmission).
Note:
In view of the combined gain and the complexity of TTI bundling, interference
location change in the four subframes of TTI bundling is not handled.
The following cell-level parameters determine whether FSS or NFSS is used for the
frequency domain scheduling strategy:
 PhyChannel.freqSelectDl: It is set to "Downlink PRB randomization" by default, indicating

that the downlink PRB randomization allocation mode is used. If it is set to "RB location
sub-band allocation", the FSS mode is used.
 PhyChannel.freqSelectUl: It is set to "Uplink PRB randomization[6]" by default, indicating

that the uplink PRB randomization allocation mode is used. If it is set to "RB location
sub-band allocation", the FSS mode is used.
3.2.8 Uplink TTI Bundling
3.2.8.1 Basic Principle
UEs at cell edge are limited to uplink power. TTI bundling is used to reduce the BLER
and transmission delay of VoIP services for only uplink transmission at cell edge.
If the activation requirements are satisfied, the same TB is transmitted on four

consecutive uplink subframes, which is called one bundling. The size of one TTI
bundling is 4 in FDD mode. The UE detects uplink authorization only on the first
subframe of the bundling, and the eNodeB sends an ACK or NACK message on
subframe N+4 if the fourth subframe is N. If retransmission is required, the same TB
is also transmitted on four consecutive uplink subframes.
3.2.8.2 Scheduling Policies
Uplink TTI bundling activation requires that the SINR of a cell edge subscriber is
lower than the threshold of the TTI bundling SINR (hard code: 4dBm) and the path
loss is higher than the threshold of the TTI bundling path loss. If the requirement is
satisfied, the uplink TTI bundling is activated for the subscriber, and an RRC
connection reconfiguration bundling message is simultaneously sent to the
subscriber. If the requirement is not satisfied, even Switch of TTI Bundling is
configured to “enabled”, the uplink TTI bundling is disabled.
Uplink TTI bundling deactivation requires that the SINR of a cell edge subscriber with
the enabled TTI bundling is higher than the threshold of the TTI bundling SINR (Out
TTI Bundling SINR Threshold) or the path loss is lower than the threshold of the TTI
bundling path loss . If the requirement is satisfied, the uplink TTI bundling is
deactivated, and an RRC connection re-setup message is sent to the subscriber. If
the requirement is not satisfied, the uplink TTI bundling is still activated.
If the number of RBs is 1, 2, and 3, and the TTI bundling uses the broadband SINR
for transmission.
3.2.8.3 HARQ Process
There are four HARQ processes on an uplink TTI bundling in FDD mode. In one TTI
bundling, the HARQ processes are the same.
At each TTI, redundant version data is sent in a single HARQ process, and does not
need to wait for HARQ response. After data at the final TTI is received, an HARQ
response is sent. Because the LTE uplink supports the synchronous HARQ
technology, HARQ retransmission must be processed. Figure 3-19 shows the HARQ
time sequence in the TTI bundling.
Figure 3-13 TTI Bundling HARQ Time Sequence
3.2.9 DRX
3.2.9.1 Basic Principle
Discontinuous Reception (DRX) refers to a RRC_CONNECTED UE's discontinuous

reception of a PDCCH scrambled with C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-
RNTI and Semi-Persistent Scheduling C-RNTI (if configured). If the DRX function is
configured for a UE in an RRC message, the UE can discontinuously listen to the
PDCCH to minimize UE transmit power.
The figure below shows how the DRX works. The UE detects and receives the
PDCCH scrambled with RNTIs mentioned above periodically within the active time,
while it does not perform such operations in the sleeping status.
Figure 3-14 DRX Principle
DRX cycle: interval of repeated DRX, which can be divided into long cycle and short
cycle. Based on different cycles, the DRX function can be divided into Long DRX
and Short DRX. When DRX is enabled, Long DRX is enabled by default, while Short
DRX can be optionally enabled. When Short DRX is enabled, the cycle of Long DRX
is an integral multiple of that of Short DRX.
On Duration: start of one DRX cycle. In this duration, the UE can listen for the
PDCCH in active status.
Opportunity for DRX: duration other than On Duration in one DRX cycle. In this
duration, the UE may be active or sleep, and does not listen for the PDCCH.
In this version, the DRX-related timers are as follows:
1. On Duration timer (one timer is provided for each UE)
 – Enabled:
 If Short DRX is enabled, On Duration Timer is enabled when the following

requirement is satisfied:
[(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset)
modulo(shortDRX-Cycle)
 If Long DRX is enabled, On Duration Timer is enabled when the following

requirement is satisfied:
[(SFN * 10) + sub-frame number] modulo (Long DRX Cycle) = DRX Start
Offset
 – Disabled:
 On Duration Timer expiration
2. DRX Inactivity timer (one timer is provided for each UE)
 Enabled:
 The uplink or downlink PDCCH with initial transmission is received
 Disabled:
 DRX Inactivity Timer expiration
3. Short Cycle timer (one timer is provided for each UE)
 Enabled:
 A short cycle is configured and InactivityTimer starts or restarts at expiration.
 Disabled:
 ShortCycle Timer expiration
4. HARQ RTT timer (one timer is provided for each HARQ process of a UE)
 Enabled:
 Downlink data (downlink initial transmission, retransmission, and SPS data) of the
process is received
 Disabled:
 Timer expiration
5. DRX Retransmission timer (one timer is provided for each HARQ process of a UE)
 Enabled:
 The HARQ RTT timer of the corresponding process expires, and the data of the
process fails to be transmitted
 Disabled:
 Downlink data (downlink initial transmission, retransmission, and SPS data) of the
process is received
Note:
 The CQIs/PMIs/RIs or SRSs on the PUCCH are sent only when the UE is in active
status
 The UE sends or receives HARQs when necessary, no matter whether the UE is

monitoring the PDCCH or not.
3.2.9.2 DRX Impact on Scheduling
The UE in DRX sleep status does not listen to the PDCCH, and thus the eNodeB
does not perform uplink and downlink scheduling for the UE. If the UE needs to
transmit uplink data, however, it can also initiate a scheduling request in DRX sleep
status.
After receiving the PDCCH, the UE changes to active status. After the corresponding
timer expires, the UE returns to sleep status.
The figures show the uplink and downlink scheduling flows after the DRX function is
enabled.
Figure 3-15 DRX Impact on Uplink Scheduling
From the figure above, the eNodeB does not perform uplink scheduling for the UE in
DRX sleep status.
Figure 3-16 DRX Impact on Downlink Scheduling
From the figure above, the eNodeB does not perform downlink scheduling for the
UE in DRX sleep status.
Operators can configure the following DRX parameters:
 switchForGbrDrx: DRX switch for GBR services
When switchForGbrDrx is set to On, GBR service DRX is enabled by default.
 switchForNGbrDrx: DRX switch for NGBR services
When switchForNGbrDrx is set to On, NGBR service DRX is enabled by default.
Other configurable DRX-related parameters are listed below:
If switchForGbrDrx is set to on, the DRX function of GBR services is enabled.
If switchForNGbrDrx is set to on, the DRX function of NGBR services is enabled.
Other configurable DRX-related parameters are specified as follows:
 ucShortDrxCycInd: whether to support the short DRX
 ucLongDrxCyc: length of the long DRX cycle

 ucShortDrxCyc: length of the short DRX cycle
 ucShortDrxCycT: length of the short DRX cycle timer
 ucOnDuratTimer: length of the OnDuration timer
 ucDrxInactTimer: length of DRX InactivityTimer
 ucDrxRetranTimer: length of the DRX retransmission timer
3.2.10 Random Access
Random access scheduling includes three scheduling messages: Msg1, Msg2, and
Msg3.
The section only describes the scheduling schemes of random access process.
3.2.10.1 Msg1 Scheduling
Msg1 is transmitted on the PRACH. The scheduling for PRACH resources is

preemptive, and thus Msg1 scheduling has no detailed policy.
3.2.10.2 Msg2 and Msg3 Scheduling
1. Principle
After Msg1 is scheduled, the scheduler packetizes the Msg2 (RAR) and
schedules the Msg2 before common scheduling (for example, BCCH, PCCH, CCCH,
and dynamic scheduling).
Figure 3-17 Msg2 and Msg3 Scheduling Sequence
When the UE detects the random access process on the initial PRACH of Msg2 in a Random
Access Response (RAR) window, the RAR window starts after 2ms. The size of the RAR
window is configurable.
2. Msg3 uplink authorization
The TBS of Msg3 is determined by the Msg3 contents.
Table 3-1 Relationship between Msg3 TBSs and Msg3 Contents
Random Access Trigger Msg3 Content Msg3 TBS

RRC connection setup RRC connection request + CRC + 80 bits
MAC subheader
RRC connection setup RRC connection reconfiguration 80 bits
request + CRC + MAC subheader
Handover C-RNTI + Handover completion > 80 bits
message + BSR + 3 MAC subheaders
+ CRC
Downlink out-of- C-RNTI + CRC 48 bits
synchronization, but downlink
data arrives
Uplink out-of-synchronization, C-RNTI + BSR + MAC subheader + 64 bits or
but uplink data arrives CRC 80 bits
If a handover triggers random access and Random Access Preambles group B is

used, the TBS of Msg3 is 208 bits. For other handover-triggered random access, the
TBS of Msg3 IS 56 bits.
To guarantee coverage, the number of RBs and the MCS are allocated according to
low bitrates. The RBs are allocated from the start of low frequencies.
3. Msg3 HARQ
Msg3 is the first available message of HARQ retransmission. The maximum number of
Msg3 HARQ retransmissions can be configured through the maxHarqMsg3Tx
parameter to obtain the maximum success rate of RRC connection setup.
The following parameters can be configured:
 raResponseWindowSize: size of the random access response window
 maxHarqMsg3Tx: maximum number of Msg3 HARQ retransmissions

3.2.11 SPS
3.2.11.1 Principle
In Semi-Persistent Scheduling (SPS), the eNodeB indicates the current scheduling

information (for example, RB, MCS, and HARQ) to a UE through the PDCCH
scheduling content in initial transmission. The UE identifies SPS by PDCCH
scrambling. If the PDCCH of initial scheduling is scrambled with SPS-C-RNTI, the
UE regards the scheduling as SPS and saves the current scheduling information. At
regular intervals, the UE sends and receives data at the same time domain and
frequency domain. For periodic packets, SPS keeps activated after the first
authorization to minimize PDCCH resources that indicate scheduling resources.
Therefore, the system can support more voice subscribers through SPS under the
precondition of guaranteeing voice quality and system performance. In addition, SPS
can save control information for dynamic scheduling services.
The following uses VoIP services as an example. Based on data arrival at an interval
of 20 ms, the eNodeB sets the scheduling interval to 20SPS, and then sends the
SPS indication to the UE through the PDCCH. The UE starts to send and receive
data according to the PDCCH indication. The UE sends and receives new data at
the same time domain and frequency domain at an interval of 20ms. In the figure
below, the green blocks indicate the intervals of UE sending and receiving data.
Figure 3-18 UE Sending and Receiving Intervals
3.2.11.2 Uplink SPS
To guarantee channel quality, maximum frequency spectrum usage, and system

capacity, the uplink scheduler of the eNodeB activates, deactivates, or reactivates
SPS status according to a service property, a bearer type, and channel quality of the
current UE.
Uplink SPS activation: The uplink scheduler of the eNodeB activates the SPS of a
UE according to a service property and channel quality indication. After the SPS is
activated, DCI0 is not retransmitted at the specified intervals. The MCS is calculated
on the AMC module (refer to section 3.2.5). If the calculated MCS is less than 2, the
eNodeB does not activate the MCS. If the total number of RBs allocated to the UE
is more than 30% of the system bandwidth, the UE cannot activate the SPS.
Uplink SPS reactivation: After the UE activates the SPS, the eNodeB reschedules
time-domain and frequency-domain resources if the channel quality of the UE
changes. SPS reactivation is required if any of the following requirements is satisfied:
1. When the CRC ERROR through SPS reaches the corresponding threshold or the CRC
OD reaches the corresponding threshold, and the re-calculated MCS is not equal to the
one previously scheduled.
2. When the RRC connection with bearer establishment or release is re-configured, and
the SPS service size changes compared with that when SPS is activated.
3. The ICIC function is enabled, and the UE property changes.
4. SPS resource conflict occurs between two UEs in initial transmission.
When the UE receives the deactivation indication from the eNodeB, the cell
deactivates the SPS. After receiving the LCG 1 BSR being 0, if the UE does not
receive the LCG 1 BSR for the three consecutive scheduling periods or still receives
the LCG 1 BSR being 0, the SPS is deactivated.
If the UE enables the TTI bundling function, the SPS is disabled. After the TTI
bundling function is disabled, the SPS is automatically enabled.
If the SPS for initial transmission fails, HARQ retransmission is used. The RNTI in
retransmission uses SPS-C-RNTI.
3.2.11.3 Downlink SPS
Downlink SPS is similar to uplink SPS. The difference between them is as follows:
LTE downlink HARQ is asynchronous transmission by default. Therefore, the

eNodeB selects an HARQ process according to the special requirements in the
protocol to guarantee that the retransmitted data can be properly combined.
The activation, deactivation, and reactivation of downlink SPS is based on the

current transmission mode. The eNodeB selects the corresponding DCI for downlink
SPS according to different transmission modes. DCI 1A is used if a UE releases
DLSPS resources. Table 3-2 describes the SPS C-RNTI configurations for the
PDCCH and PDSCH In this version, DCI 1A is used for SPS activation, deactivation
and reactivation.
Table 3-2 SPS C-RNTI Configurations for the PDCCH and PDSCH
Transmission DCI format Search Space Transmission scheme of

mode PDSCH corresponding to
PDCCH
Mode 1 DCI format Common and Single-antenna port, port 0
1A UE specific by C- (see subclause 7.1.1)
RNTI
DCI format 1 UE specific by C- Single-antenna port, port 0
RNTI (see subclause 7.1.1)
Mode 2 DCI format Common and Transmit diversity (see
1A UE specific by C- subclause 7.1.2)
RNTI
DCI format 1 UE specific by C- Transmit diversity (see
RNTI subclause 7.1.2)
RNTI
DCI format UE specific by C- Transmit diversity (see
2A RNTI subclause 7.1.2)
RNTI
DCI format 2 UE specific by C- Transmit diversity (see
RNTI subclause 7.1.2)

RNTI
RNTI
RNTI
DCI format 1 UE specific by C- Single-antenna port, port 5
RNTI (see subclause 7.1.1)
Mode 8 DCI format Common and Single-antenna port, port
1A UE specific by C- 7(see subclause 7.1.1)
RNTI
DCI format UE specific by C- Single-antenna port, port 7 or
2B RNTI 8 (see subclause 7.1.1)
Transmission DCI format Search Space Transmission scheme of
mode PDSCH corresponding to
PDCCH
RNTI
DCI format UE specific by C- Single-antenna port, port 7 or
2C RNTI 8, (see subclause 7.1.1)
4 Engineering Guide
4.1 Related parameters
4.1.1 Related parameters for Scheduling Policy
Table 4-1 Rule of scheduling policy parameter configuration
Parameter Range vale Unit Default

Parameter
SN Parameter name panel Value
explanation
name
The 0:EPF,
Scheduler scheduler
1 EMLP.schedulerAlg 1:RR, N/A EPF[0]
Algorithm algorithm for
the eMLP. 2:SPS
α factor for
Alpha numerator
2 EMLP.alpha [0..10] step 1 N/A 10
Factor of PF sub-
fair factor
β factor for
Beta denominator
3 EMLP.beta [0..10] step 1 N/A 10
Factor of PF sub-
fairfactor
The weight
of PF sub-
PF Weight fair factor
4 EMLP.pFWeight [0..20] step 1 N/A 10
Factor used for
priority
calculation
The weight
of GBR sub-
GBR
fair factor
5 EMLP.gBRWeight Weight [0..20] step 1 N/A 10
used for
Factor
priority
calculation
Parameter Range vale Unit Default
Parameter
SN Parameter name panel Value
explanation
name
The weight
of AMBR
AMBR
sub-fair
6 EMLP.aMBRWeight Weight [0..20] step 1 N/A 10
factor used
Factor
for priority
calculation
The weight
of Delay
Delay
sub-fair
7 EMLP.delayRWeight Weight [0..20] step 1 N/A 10
factor used
Factor
for priority
calculation
The weight
Scheduling of QCI sub-
Weight fair factor
8 EMLP.aRPWeight [0..20] step 1 N/A 10
Factor for used for
All ARP priority
calculation
The weight
Scheduling of ARP sub-
Weight fair factor
9 EMLP.qCIWeight [0..20] step 1 N/A 10
Factor for used for
All QCIs priority
calculation
The weight
of service
Service
sub-fair
10 EMLP.serviceWeight Weight [0..20] step 1 N/A 0
factor used
Factor
for priority
calculation
PBR is used
for logical
channel
resource
scheduling
Prioritized [0..10000000] 32
11 QoSPBRMapping.pbrValue by MAC kbps
Bit Rate step 1
layer, and
reflects the
demand of
bearer to
resource.
4.1.2 Related parameters for QoS
Please refer to ZTE LTE FDD QoS Feature Guide.

4.1.3 Related parameters for PDCCH and CFI Allocation
Table 4-2 PDCCH and CFI allocation parameters configuration rule
Parameter Range Unit Default

Parameter
SN Parameter name panel Value Value
explanation
name
The 0: Auto- N/A 2
parameter Adjusted,
indicates 1:1
the CFI 2:2
Value
3:3
configured
by high 4:4
CFI layer for
1 EUtranCellFDD.cFI
Selection cell. The
CFI Value
could be 1,
2, 3 or could
be
configured
as auto-
adjusted.
0: 1,
1: 2,
The CCE CCE Adaption
2 EUtranCellFDD.cceAdaptMod 2: 4, N/A
Aggregation Aggregation [4]
3: 8,
4:Adaption
4.1.4 Related parameters for Uplink and Downlink Frequency Selection
Table 4-3 Rule of uplink and downlink frequency selection parameters
Range Value Un Defa

Parameter Parameter
S it ult
Parameter name panel explanatio
N Valu
name n
e
The 0: RB Location N/ 6
parameter Wideband A
indicates Allocation,1: RB
the uplink Location Sub-
frequency Band
selection Allocation(Frequ
configured ency
by high Selective),2: UL
layer for Hopping(Non-
cell. The Frequency
parameter Selective),3:
is Speed Self
configured Adaption,4:
by Service Self
enumerate Adaption,5: Self
number. Adaption,6:
The Uplink PRB
frequency Random
selection Allocation,7:Alloc
could be ate RB from high
Uplink
RB frequency
1 PhyChannel.freqSelectUl Frequency
bandwidth
Selection
allocation
(frequency
selection),
RB
subband
allocation
(frequency
selection),
hop
frequency
(non-
frequency
selection),
speed auto-
adjusted,
service
auto-
adjusted,
auto-
adjusted.
Range Value Un Defa
Parameter Parameter
S it ult
N Valu
name n
e
The 0: RB Location N/ 2
parameter Wideband A
indicates Allocation,
the 1: RB Location
downlink Sub-Band
frequency Allocation(Frequ
selection ency-Selective),
configured 2: Downlink PRB
by high Random
layer for Allocation,
cell. The
3: Speed Self
parameter
Adaption,
is
configured 4: Service Self
by Adaption,
enumerate 5: Self Adaption
number.
The
frequency
Downlink selection
2 PhyChannel.freqSelectDl Frequency could be
Selection RB
bandwidth
allocation
(frequency
selection),
RB
subband
allocation
(frequency
selection),
PRB
Random
Allocation,
speed auto-
adjusted,
service
auto-
adjusted,
auto-
adjusted.
Range Value Un Defa
Parameter Parameter
S it ult
N Valu
name n
e
The 0: Wideband N/ 1
parameter Feedback, A
indicates 1: Higher Layer-
the Configured
methods of Subband
a periodic Feedback,
feedbackin 2: UE-Selected
g CQI on Subbands
PUSCH for Feedback
each
transmissio
The
n mode.
Method of
There are
3 PhyChannel.puschCqiFbMethd Feedbackin
three
g CQI for
methods,
PUSCH
Wideband
feedback,
higher
Layer-
configured
subband
feedback,
UE
Selected
subband
feedback.
The 0:Close, N/ 0
parameter 1: Open A
The Switch
indicates
of SRS
4 PhyChannel.srsEnable the switch
Configurati
of SRS
on
Configurati
on.
Range Value Un Defa
Parameter Parameter
S it ult
N Valu
name n
e
QCI1 0: N/ 0
NI Close,1: A
Freque Open Only
ncy for Newtx,2:
Select Open Only
Switch, for Retx,
0- 3:
close,1 Both for
QCI1 Newtx and
-open
NI Retx
VoLTEConfigCell.switchOfFreq only
Freque
5 for
Sel4Ni ncy
newtx,
Select
2-open
Switch
only
for
retx,3-
both
for
newtx
and
retx
4.1.5 Related parameters for Adaptive DL MIMO Modes
Please refer to ZTE LTE FDD DL MIMO Feature Guide.
4.1.6 Related parameters for UL TTI Bundling
Table 4-4 Rule of UL TTI bundling parameter configuration

Parameter
explanation
name
The 0: N/A 0
parameter Close,1:
Switch of determines Open
1 PhyChannel.swchTTIBundling TTI whether cell
Bundling applies TTI
Bundling or
not.
Parameter
explanation
name
When UE' [0..30] dB 4
service type
includes
QCI1, Use
the
parameter
Open TTI to provides
Bundling SINR
SINR threshold to
Threshold determine
2 PhyChannel.ttiBundSinrIn4QCI1 When UE' whether UE
Service applies TTI
Type Bundling or
Includes not. If UE
QCI1 SINR is less
than the
threshold,
UE will be
configured
in bundling
operation.
When UE' [0..30] dB 8
service
includes
QCI1, the
parameter
provides
SINR
Close TTI
threshold to
Bundling
determine
SINR
whether UE
Threshold
applies TTI
3 PhyChannel.ttiBundSinrOut4QCI1 When UE'
Bundling or
Service
not. If UE
Type
SINR is
Includes
more than
QCI1
the
threshold,
UE will be
configured
in normal
HARQ
operation.
Parameter
explanation
name
When UE' [0..30] dB 0
service type
does not
includes
QCI1, Use
the
parameter
to provides
Open TTI SINR
Bundling threshold to
SINR determine
4 PhyChannel.ttiBundSinrIn
Threshold whether UE
Except applies TTI
QCI1 Bundling or
not. If UE
SINR is less
than the
threshold,
UE will be
configured
in bundling
operation.
When UE' [0..30] dB 4
service does
not include
QCI1, use
the
parameter
provides
SINR
threshold to
Close TTI
determine
Bundling
whether UE
SINR
5 PhyChannel.ttiBundSinrOut applies TTI
Threshold
Bundling or
Except
not. If UE
QCI1
SINR is
more than
the
threshold,
UE will be
configured
in normal
HARQ
operation.
Parameter
explanation
name
The [50..160] N/A 132
parameter
provides PL
Open TTI
threshold to
Bundling
6 PhyChannel.ttiBundPlIn determine
PL
whether UE
Threshold
applies TTI
Bundling or
not.
The [50..160] N/A 128
parameter
provides PL
threshold to
Close TTI determine
Bundling whether UE
7 PhyChannel.ttiBundPlOut
PL return
Threshold normal
transmission
form TTI
Bundling or
not.
4.1.7 Related parameters for DRX
Table 4-5 Rule of DRX parameters configuration
Range Uni Defaul

S Parameter Parameter
Parameter name Value t t
N panel name explanation
Value
The DRX Switch
for GBR service
controls whether
DRX for GBR
service is closed
or not. If he DRX
0:Close
EUtranCellFDD.switchForGbrDr DRX Switch Switch for GBR
1 , N/A 1
x for GBR service is
closed, 1:Open
discontinuous
reception (DRX)
cannot be used
for a UE with
GBR services.
Range Uni Defaul
Value
The DRX Switch
for NGBR
service controls
whether DRX for
NGBR service is
closed or not. If
he DRX Switch 0:Close
EUtranCellFDD.switchForNGbr DRX Switch ,
2 for NGBR N/A 1
Drx for NGBR
service is 1:Open
closed,
discontinuous
reception (DRX)
cannot be used
for a UE with
NGBR services.
Identifies UE
short DRX
capacity to
select
configuration, is
a complete set
of configuration
of the primary
key, on the
basis of the UE
capacity
matching
UE Short
corresponding
DRX Cycle
DRX 0:No,
3 ServiceDrx.shortDrxCycInd Capacity N/A 0
configuration 1:Yes
Configuration
parameters,
Indicator
when UE able to
support short
DRX, the
ucShortDrxCycI
nd choice for
True
configuration.
Otherwise
ucShortDrxCycI
nd choice for
False
configuration
Range Uni Defaul
Value
0:10,
1:20,
2:32,
3:40,
4:64,
5:80,
Long DRX cycle 6:128,
Specifies the 7:160,
periodic 8:256,
Long DRX repetition of the 9:320,
4 ServiceDrx.longDrxCyc sf 9
Cycle On Duration
10:512,
followed by a
possible period 11:640,
of inactivity 12:102
4,
13:128
0,
14:204
8,
15:256
0
0:2,
1:5,
2:8,
3:10,
4:16,
Short DRX cycle
Specifies the 5:20,
periodic 6:32,
Short DRX repetition of the 7:40,
5 ServiceDrx.shortDrxCyc sf 7
Cycle On Duration 8:64,
followed by a 9:80,
possible period
10:128,
of inactivity,
11:160,
12:256,
13:320,
14:512,
15:640
Specifies the
number of
consecutive
DRX Short
6 ServiceDrx.shortDrxCycT subframe(s) the [1..16] N/A 4
Cycle Timer
UE shall follow
the Short DRX
cycle
Range Uni Defaul
Value
0:1,
1:2,
2:3,
Specifies the 3:4,
number of
4:5,
consecutive
PDCCH- 5:6,
subframe(s) at 6:8,
On Duration the beginning of 7:10,
7 ServiceDrx.onDuratTimer psf 8
Timer a DRX Cycle, 8:20,
during which the 9:30,
UE monitors the
10:40,
PDCCH in
PDCCH- 11:50,
subframes, 12:60,
13:80,
14:100,
15:200
0:1,
1:2,
2:3,
3:4,
4:5,
5:6,
6:8,
Specifies the 7:10,
number of
8:20,
consecutive
PDCCH- 9:30,
subframe(s) 10:40,
after 11:50,
DRX Inactivity successfully 12:60,
8 ServiceDrx.drxInactTimer psf 10
Timer decoding a 13:80,
PDCCH
indicating an 14:100,
initial UL or DL 15:200,
user data 16:300,
transmission for 17:500,
this UE. 18:750,
19:128
0,
20:192
0,
21:256
0,
22:0
Range Uni Defaul
Value
Specifies the
0:1,
maximum
number of 1:2,
consecutive 2:4,
DRX
PDCCH- 3:6,
9 ServiceDrx.drxRetranTimer Retransmissio psf 4
subframe(s) for 4:8,
n Timer
as soon as a DL 5:16,
retransmission
6:24,
is expected by
the UE. 7:33
4.1.8 Related parameters for Scheduling in Random Access
Table 4-6 Rule of random access parameters configuration
Parame Range Value Un Def

S ter Parameter it ault
Parameter name
N panel explanation Val
name ue
The parameter
indicates the frame
number and subframe
number configuration,
via different
configurations,
different opportunity
used to transmit
Prach
PRACH is also
PrachFDD.prachConfigI Configu [0..29],[31..45],[47. N/
1 configured. In fact, 5
ndex ration .59],[63..63] A
the parameter gives
Index
the access
opportunity for
PRACH. The larger
the number of frame
and subframe used to
transmit PRACH is,
the more the access
opportunity is.
Starting
RB
The parameter is
Number
used to determine the
of
PrachFDD.prachFreqOff frequency position N/
2 Rando [0..94] 0
set used for PRACH. The A
m
PRACH uses 6 RB,
Access
from 0 to N_RB^UL-6.
Preamb
le
Parameter name
name ue
The parameter 0: Not High Speed N/ 0
indicates whether the Cell, A
cell is high-speed. If 1: High Speed Cell
cell high-speed
attribute is high-
speed, The cyclic shift
Cell
method to generate
High-
PrachFDD.highSpeedFla PRACH preamble
3 Speed
g sequence is different
Attribut
between high-speed
e
cell and non high-
speed cell. In high-
speed cell, cyclic shift
is restricted. In non
high-speed cell, cyclic
shift is not restricted.
Number [0..837] N/ 0
of A
Rando
m
Access
The parameter
Preamb
defines the number of
PrachFDD.numberOfRA le
4 contention based
Preambles Signatu
random access
res
preambles.
Based
on
Content
ion
Conflict
Parameter name
name ue
The parameter
indicates the logical
root sequence start
number used to
generate prach
preamble. There are
64 preambles
available in each cell.
The set of 64
preamble sequences
in a cell is found by
including first, in the
order of increasing
Starting cyclic shift, all the
Index of available cyclic shifts
Logical of a root Zadoff-Chu
Root sequence with the
PrachFDD.rootSequenc Sequen logical index N/
5 [0..15] 10
eIndex ce to RACH_ROOT_SEQU A
Generat ENCE, where
e 64 RACH_ROOT_SEQU
Preamb ENCE is broadcasted
le as part of the System
Information.
Additional preamble
sequences, in case
64 preambles cannot
be generated from a
single root Zadoff-
Chu sequence, are
obtained from the root
sequences with the
consecutive logical
indexes until all the
64 sequences are
found.
Parameter name
name ue
The parameter is
used to determine the
shift number of cyclic
shift. There are 64
preambles available
in each cell. The set
of 64 preamble
sequences in a cell is
found by including 0:4,
first, in the order of 1:8,
increasing cyclic shift, 2:12,
all the available cyclic 3:16,
Cyclic
shifts (correlative to
Shift 4:20,
Ncs) of a root Zadoff-
Parame 5:24,
Chu sequence with
ters 6:28,
the logical index
Based
RACH_ROOT_SEQU 7:32, N/
6 PrachFDD.ncs on 12
ENCE, where 8:36, A
Logical
RACH_ROOT_SEQU 9:40,
Root
ENCE is broadcasted
Sequen 10:44,
as part of the System
ce 11:48,
Information.
(Ncs) 12:52,
Additional preamble
sequences, in case 13:56,
64 preambles cannot 14:60,
be generated from a 15:64
single root Zadoff-
Chu sequence, are
obtained from the root
sequences with the
consecutive logical
indexes until all the
64 sequences are
found.
Parameter name
name ue
0:4,
1:8,
2:12,
3:16,
Number 4:20,
of 5:24,
The parameter
Preamb 6:28,
defines the number of
PrachFDD.sizeOfRAPre le N/
7 Random Access 7:32, 11
amblesGroupA Signatu A
preambles in Group 8:36,
res in
A. 9:40,
Group
A 10:44,
11:48,
12:52,
13:56,
14:60
If no Random Access
Response is received
by UE after UE
transmitted Random
Access Preamble, UE
will increase transmit
PRACH power for PRACH by 0:0,
PrachFDD.powerRampin Power Power step and retry 1:2,
8 dB 1
gStep Ascendi to transmit Random 2:4,
ng Step Access Preamble 3:6
until
Preamble_Transmissi
on_Counter is equal
to
Max_retransmit_num
ber_for_prach.
If no Random Access
Response is received
by UE after UE 0:3,
transmitted Random 1:4,
Maximu
Access Preamble, UE 2:5,
m
will increase transmit 3:6,
Transmi
power for PRACH by 4:7,
ssion
PrachFDD.preambleTra Power step and retry N/
9 Times 5:8, 5
nsMax to transmit Random A
of 6:10,
Access Preamble
PRACH 7:20,
until
Preamb
Preamble_Transmissi 8:50,
le
on_Counter is equal 9:100,
to
10:200
Max_retransmit_num
ber_for_prach.
Parameter name
name ue
0:-120,
1:-118,
2:-116,
3:-114,
4:-112,
PRACH 5:-110,
Initial The parameter 6:-108,
Preamb indicates initial power
1 PrachFDD.preambleIniR 7:-106, dB
le for preamble of 10
0 eceivedPower 8:-104, m
Transmi PRACH. It is that the
ssion first transmit power. 9:-102,
Power 10:-100,
11:-98,
12:-96,
13:-94,
14:-92,
15:-90
Messag
e
Based on this
Length
parameter of 0:56,
of
message3 size, UE
1 PrachFDD.messageSize Rando 1:144, bit
determines to select 0
1 GroupA m 2:208, s
the Random Access
Access 3:256
Preambles group A or
Preamb
group B.
le
Group
Transmi The parameter is a 0:Minusinfinity,
ssion power control margin 1:0,
Power for message 3 2:5,
Offset transmission
1 PrachFDD.messagePow 3:8,
of configured by the dB 3
2 erOffsetGroupB 4:10,
Group eNB and is used to
B select the Random 5:12,
Preamb Access Preambles 6:15,
le group A or group B. 7:18
Parameter name
name ue
Once the Random
Receivi Access Preamble is
ng transmitted, the UE
0:2,
Search shall monitor the
Window PDCCH in the TTI 1:3,
for window 2:4,
1 PrachFDD.raResponse Rando [RA_WINDOW_BEGI 3:5, m
7
3 WindowSize m N- 4:6, s
Access RA_WINDOW_END] 5:7,
Preamb for Random Access
6:8,
le Response(s). The
Respon parameter indicates 7:10
se (ms) the monitor window
size.
Maximu
m
Transmi In the random access
1 PrachFDD.maxHarqMsg ssion procedure, the max N/
[1..8] 5
4 3Tx Times number of messages A
of 3 harq transmissions.
Messag
e3
The [0..58] N/ 2
Number A
of Non-
Content This parameter
ion defines the number of
1 PrachFDD.macNonCont
Rando non-contention
5 enPreamble
m Random Access
Access preambles for MAC.
Preamb
les for
MAC
Parameter name
name ue
In the random access 0:8, sf 7
procedure, once the 1:16,
uplink message 2:24,
containing the C- 3:32,
RNTI MAC control 4:40,
element or the uplink 5:48,
message including 6:56,
CCCH is transmitted, 7:64
MAC Contention
Resolution Timer will
MAC
be started. If MAC
Content
Contention Resolution
1 PrachFDD.macContRes ion
Timer is running, UE
6 Timer Resoluti
will detect PDCCH
on
and wait for the
Timer
response from
network and
determine whether it
is allowed to access
network. If the MAC
Timer expires, UE
considers this
not successful.
The The switch of PRACH 0: Adaptive, N/ 0
Switch starting RB 1: Manual A
of configuration method.
PRACH Zero means
1 PrachFDD.prachFreqOff
Starting PrachFreqOffset is
7 setFlag
RB adaptive , and one
Configu means
ration PrachFreqOffset is
Method manual configured.
This parameter is in 0: Close, N/ 0
Normal coverage and 1: A
Switch
High way coverage, Open
for
for PRACH ultimate
1 PrachFDD.prachUltiCap PRACH
capacity test, opened
8 Swch Ultimate
in the PRACH
Capacit
ultimate capacity test,
y Test
the other is turned off
by default.
4.1.9 Related parameters for SPS Configuration
Table 4-7 Rule of SPS parameters configuration
Parame Paramet Range Value Un Default Value

S ter er it
Parameter name
N panel explanat
name ion
The
Schedul schedule 0:EPF,
er r N/
1 EMLP.schedulerAlg 1:RR, 0
Algorith algorithm A
m for the 2:SPS
eMLP.
Number
Number of
of PUCCH
PUCCH Channel {pucchDeltaShf==0}[ {pucchDeltaShf=
Channel for 0..2046] step 3, =0}[0],
for ACK/NA
PhyChannel.pucchSe {pucchDeltaShf==1}[ N/ {pucchDeltaShf=
2 ACK/NA CK of
miAnNum 0..2046] step 3, A =1}[0],
CK of Downlink
Downlin SPS {pucchDeltaShf==2}[ {pucchDeltaShf=
k SPS Scheduli 0..2047] step 1 =2}[0]
Schedul ng in one
ing subfram
e
4.2 Related Counters, KPI and Alarms
4.2.1 Related Counters
Table 4-8 Descriptions for PDCCH and CFI Allocation Counters
SN. Counter No. Description

1 C373424604 CCE Number Used on PDCCH Channel
2 C373424605 CCE Number Available on PDCCH Channel

3 C373424643 Number of CCE Aggregation Level 1

Table 4-9 Descriptions for UL TTI Bundling Counters

1 C373424688 Number of TTI Bundling Activation Request
2 C373424689 Number of TTI Bundling Activation Completed

3 C373424690 Number of TTI Bundling Deactivation Request
4 C373424691 Number of TTI Bundling Deactivation Completed
5 C373424692 Data Volume of Scheduled UE within the

Threshold
6 C373424693 Number of Scheduled UE within the Threshold
7 C373424694 Number of TTI Bundling Scheduled UE within the

Threshold
8 C373424695 Error Number of TB within the Threshold
9 C373424696 Total Number of TB within the Threshold
Table 4-10 Descriptions for Scheduling in Random Access Counters
1 C373444757 Number of No RACH Dedicate Preamble Assigned
C373444758 Total Number of RACH Dedicate Preamble

2 Assigned
3 C373444759 Number of Sent Msg2 by ENB
C373444761 Times of Contention Based Random Access

4 Initiated by Handover
C373444762 Times of Non-Contention Based Random Access
5 Initiated by Handover
4.2.2 Related KPI
None
4.2.3 Related Alarms
None
4.3 Application Scenarios
4.3.1 Hardware Requirements
No special requirements
4.3.2 EPC Requirements
4.3.3 Frequency Band, Frequency and Bandwidth Requirements of Frequency Carrier
4.3.4 UE Requirement
DRX, TTI Bundling and SPS require UE support the corresponding function.
4.3.5 Transmission Bandwidth Requirements
4.4 Parameter Configuration Procedure
4.4.1 Scheduling Policy Configuration
4.4.1.1 Enabling the Feature
Scheduling Policy is enabled by default. There is no switch to disable the feature.
4.4.1.2 Configuring Other Parameters
1. In the Configuration Management window, select Modify Area > Radio Parameter >
LTE FDD > E-UTRAN FDD Cell > EMLP. The EMLP-List tab is displayed, see the
Figure below. According to "QCI mapping for eMLP" and "Logical Channel Direction" to
confirm the record to be modified.
Figure 4-1 Open the EMLP-List tab
2. Double-click the record to be modified. The EMLP tab is displayed, see the Figure
below.
Figure 4-2 Configuring the Scheduler Algorithm Parameter
3. Click the button, modify Scheduler Algorithm and other parameters according to
test requirement.
4. Click the button.
4.4.1.3 Data Synchronization
Select [Configuration Management->Data Synchronization] from the main menu

of the Configuration Management tab. The Data Synchronization dialog box opens.
First select NE, then select synchronization mode as synchronize modified data,
last click Synchronize button.
4.4.1.4 Deactivate feature
There is no switch to disable the feature.

4.4.2 QoS Configuration
Refer to ZTE LTE FDD QoS Feature Guide.
4.4.3 PDCCH and CFI Allocation Configuration

1. In the Configuration Management window, select Modify Area > Radio
Parameter > LTE FDD > E-UTRAN FDD Cell. The E-UTRAN FDD Cell tab is
displayed.
2. Click to set CFI selection to Auto-Adjusted and The CCE Aggregation to

Adaption[4], see the Figure below.
3. Click the button. The CFI and PDCCH adaption functions can be enabled at the
same time or individually as required.
Figure 4-3 Configuring PDCCH and CFI Adaption Parameters

None


displayed.
2. Click button, set CFI selection and The CCE Aggregation to a fixed value, see
the Figure below.
3. Click the button. The CFI and PDCCH adaption functions can be disabled at the
same time or individually as required.
Figure 4-4 Disable the CFI and PDCCH adaption functions
4.4.4 Link Adaptation Configuration
LTE FDD > E-UTRAN FDD Cell. The E-UTRAN FDD Cell tab is displayed.
2. Click to Modify Minimum Value of Uplink MCS, Maximum Value of Uplink MCS,
Minimum Value of Downlink MCS, Maximum Value of DownLink MCS, see the
Figure below.The default value of minimum value is 0, and the default value of maximum
value is 28. The default setting is enabing the feature.
Figure 4-5 Enabling the Link Adaptation Parameters
LTE FDD > E-UTRAN FDD Cell. The E-UTRAN FDD Cell tab is displayed.
2. Click button, set Inner AMC CQI Expire Timer, see the Figure below.
3. Click the button. The Inner AMC CQI Expire Timer is modified at the same time or
individually as required.
Figure 4-6 Inner AMC CQI Expire Timer Parameters
Select Configuration Management->Data Synchronization from the main menu


displayed.
2. Click button, set Mininum Value of MCS is equal to Maximum Value of MCS,
see the Figure below.
3. Click the button. The Link Adaptation functions can be disabled at the same time
or individually as required.
Figure 4-7 Disable Link Adaptation functions
4.4.5 Uplink and Downlink Frequency Selection Configuration
For uplink frequency selection test:

LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The PUCH and PDCH tab is
displayed.
2. Click to set Uplink Frequency Selection to RB Location Sub-Band Allocation

(Frequency Selective)[1].
Figure 4-8 Configuring Uplink Frequency Selection Switch Parameters
For downlink frequency selection test:

LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The PUCH and PDCH tab is
displayed.
2. Click to set Downlink Frequency Selection to RB Location Sub-Band

Allocation (Frequency Selective)[1], see the Figure below.
Figure 4-9 Configuring Downlink Frequency Selection Switch Parameters

For NI Based Interference Avoidance Scheduling test:
Parameter > LTE FDD > E-UTRAN FDD Cell > VoLTE
Management>QCI1 NI Frequency Select Switch. The VoLTE
Management>QCI1 NI Frequency Select Switch tab is displayed.
2. Click to set QCI1 NI Frequency Select Switch to Both for Newtx and
Retx[2] , see the Figure below.
Figure 4-10 Configuring QCI1 NI Frequency Select Switch Parameters
For downlink frequency selection test, the method of feedbacking the CQI for
PUSCH should be modified as required.
Parameter > LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The PUCH and
PDCH tab is displayed.
2. Click to set the Method of Feedbacking CQI for PUSCH to Higher Layer-
configured subband feedback[1] (default value), see the Figure below.
Figure 4-11 Configuring the Method of Feedbacking CQI for PUSCH
For uplink frequency selection test, SRS feature need to be open.

Parameter > LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The PUCH and
PDCH tab is displayed.
2. Click to set The Switch of SRS Configuration to Open[1], see the Figure
below.
Figure 4-12 Open SRS Feature

To disable uplink frequency selection:

Parameter > LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The
PUCH and PDCH tab is displayed.
2. Click to set Uplink Frequency Selection to uplink PRB Random

Allocation [6] , see the Figure below.

Figure 4-13 Disable Uplink Frequency Selection
To disable downlink frequency selection:

Parameter > LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The
PUCH and PDCH tab is displayed.
2. Click to set Downlink Frequency Selection to Downlink PRB

Random Allocation[2] , see the Figure below.

To disable NI Based Interference Avoidance Scheduling:
Parameter > LTE FDD > E-UTRAN FDD Cell > VoLTE
Management>QCI1 NI Frequency Select Switch. The VoLTE
Management>QCI1 NI Frequency Select Switch tab is displayed.
5. Click to set QCI1 NI Frequency Select Switch to Close[0] , see the

Figure below.
4.4.6 Adaptive DL MIMO Modes Configuration
Refer to ZTE LTE FDD DL MIMO Feature Guide.

4.4.7 UL TTI Bundling Configuration

Parameter > LTE FDD > E-UTRAN FDD Cell > PUCH and PDCH. The PUCH
and PDCH tab is displayed.
2. Click to set Switch of TTI Bundling to Open[1], see the Figure below.
Figure 4-16 Configuring Switch of TTI Bundling

2. Click button, configure the parameters in the figure below according to the
needs.

Figure 4-17 Configuring other parameters for TTI Bundling test (a)
Figure 4-18 Configuring other parameters for TTI Bundling test (b)

To disable the TTI bundling function, set Switch of TTI Bundling to Close[0] , see
the Figure below.
Figure 4-19 Deactivate TTI Bundling
4.4.8 DRX Configuration

Parameter > LTE FDD > E-UTRAN FDD Cell. The E-UTRAN FDD Cell tab
is displayed.
2. Click to set DRX switch for NGBR to Open[1] and DRX switch for GBR
to Open[1], see the Figure below.

Figure 4-20 Configuring DRX switch Parameters
To test the DRX parameter configuration, view or modify the DRX timer parameters:
Parameter > LTE FDD > E-UTRAN Service Configuration > Service
DRX. The Service DRX-List tab is displayed.
2. View the corresponding DRX timer parameters of QCI bearers, or click
Modify to set the parameters, see the Figure below.



displayed.
2. Click to set DRX switch for NGBR to Close[0] and DRX switch for GBR
to Close[0], see the Figure below.
Figure 4-23 Deactivate DRX feature
4.4.9 Scheduling in Random Access Configuration
Scheduling in Random Access is enabled by default. There is no switch to disable

the feature.
Parameter > LTE FDD > E-UTRAN FDD Cell > PRACH. The PRACH tab is
displayed.
2. Click to set the RACH parameters, see the Figure below.
Figure 4-24 Configuring RACH Parameters (a)

Figure 4-25 Configuring RACH Parameters (b)

The random access feature must be enabled. There is no switch to disable the
feature.
4.4.10 SPS Configuration

Parameter > LTE FDD > E-UTRAN FDD Cell > EMLP Parameter. The EMLP
Parameter-List tab is displayed, see the Figure below. Downlink EMLP
parameters are listed in the first nine line, and uplink EMPL parameters are
listed in the last nine lines. QCI mapping is listed in the QCI Mapping for EMLP
column. The marked lines indicate the parameters of “QCI=1”. ZTE
supports only the SPS scheduler algorithm corresponding to “QCI=1”.
2. Double-click the marked lines respectively. The EMLP Parameter tab is

displayed.
3. Click to set Scheduler Algorithm to SPS[2], see the Figure below.

4. Click Save, and synchronize the data to the eNode.

2. Click to set Number of PUCCH Channel for ACK/NACK of Downlink SPS

Scheduling, see the figure below.

Figure 4-28 Configuring Number of PUCCH Channel for ACK/NACK of Downlink SPS
Scheduling


Parameter > LTE FDD > E-UTRAN FDD Cell > EMLP Parameter. The EMLP
Parameter-List tab is displayed. See the Figure below.
2. Double-click the marked lines respectively. The EMLP Parameter tab is

displayed.
3. Click to set Scheduler Algorithm to EPF[0] , see the Figure below.

5 Function Validation
5.1 Scheduling Policy Function
5.1.1 Topology
For the topology of scheduling policy function test, see Figure 5-1.
Figure 5-1 Scheduling Policy Function Verification Test Architecture
For the required devices, refer to Table 5-1.
Table 5-1 Device Required for the Scheduling Policy Function Test
SN Device Remarks
1 eNodeB One
2 UE Two
3 MME One
4 PDN server One
For the scheduling policy function test specification, refer to Table 5-2.
Table 5-2 Scheduling Policy Function Test Specification
Test item Scheduling policy function test

Feature ID No
Verify that the scheduling policies supported by the system
Purpose
operate in normal status.
1. The system works properly.
Prerequisites 2. All parameters use the default value.
3. Two UEs are available and operate properly.
Step Expected step result
Check the records whose QCI
mapping of the eMLP parameter is
[9,0,0,0,0,0,0,0,0,0] and the logical
channel directions are uplink and
downlink respectively. The scheduling
algorithm used now is PF, the Alpha
1 The scheduling algorithm used is PF.
factor is 1, the Beta factor is 1, the PF
factor is 1, the GBR weight is 0, the
AMBR weight is 0, the delay weight
factor is 0, the ARP weight factor is 0,
the QCI weight factor is 0 and the
Service weight factor is 0.
Attach two UEs to the cell and make
sure UE 1 is close to eNB (RSRP>- Two UEs are attached to the cell
2
85, SINR>25), UE 2 is far from eNB successfully.
(RSRP<-105, SINR<10)
Initiate an FTP download service on The UE near to the eNB has more
3
these two UEs respectively. throughput than the UE far from eNB.
The scheduling algorithm used now is
Set the Alpha factor to 1 and Beta the MAX C/I algorithm. The UE near
4
factor to 0, and repeat steps 2-3. to the eNB has more throughput than
the UE far from eNB.
Set the Alpha factor to 0 and Beta
5 the ER algorithm. The throughput of
factor to 1, and repeat steps 2-3.
these two UEs is the same.
Set the scheduling algorithm to RR
6 the RR algorithm. The scheduling
and repeat steps 2-3.
opportunities are the same.
Traffic allocation complies with the expected result when different

Expected result scheduling algorithms are used.
Criteria The result complies with the algorithm requirements.

Test result Passed.
5.1.3 Test Result
 2UE PF algorithm traffic:
For the throughput of UE 1 (near to eNB), see Figure 5-2.
For the throughput of UE 2 (far from eNB), see the figure below.
 2UE MAX C/I algorithm throughput:
For the throughput of UE 1 (near to eNB), see the figure below...

For the throughput of UE 2 (far from eNB), see the figure below...
 2UE ER algorithm throughput:
For the throughput of UE 1 (near to eNB), see the figure below...

 2UE RR algorithm throughput:
For the throughput of UE 1 (near to eNB), see Figure 5-8.

For the PF algorithm, the throughput of these two UEs is allocated based on the
channel condition in the optimum mode. For the MAX C/I algorithm, the throughput
of these two UEs are greatly different from one to another. For the RR algorithm, the
scheduling opportunities for these two UEs are the same. From the above verification
tests, the test results comply with the expected results.
5.2 QoS
For the verification of QoS scheduling, refer to the ZTE LTE FDD QoS Feature
Guide.
5.3 PDCCH and CFI Allocation
5.3.1 Topology
For the test environment, refer to 5.1.1.
5.3.2.1 PDCCH Self-Adaptive Test Specification
For the PDCCH self-adaptive test specification, refer to Table 5-3.

Table 5-3 PDCCH Self-Adaptive Test Specification
Test item PDCCH self-adaptive function test.

Feature ID ZLF31-13-013
Verify that the PDCCH self-adaptive function can be used
Purpose
normally.
2. The system bandwidth is 20 MHz, and the UE's antenna
Prerequisites
transmission mode is self-adaptive.
3. One UE is available and it works properly.
Set the CCE Aggregation The parameter is set successfully
1 parameter to CCE Aggregation and it is synchronized to the test
Adaption eNodeB.
Move the UE to a position near to
The UE is attached to cell
2 the eNodeB and perform the
successfully.
attach operation.
Check the DCI format and CCE
Initiate an FTP download service
3 aggregation value used in
for the UE.
scheduling.
Adjust the channel condition and Check the DCI format and CCE
4 trigger the eBodeB self-adaptive aggregation value used in
to adjust the PDCCH. scheduling.
The tested UE can demodulate the PDCCH sent by
Expected eNodeB correctly.
result The eNodeB can be adaptive to the PDCCH format
according to the channel condition.
The tested UE can demodulate the PDCCH sent by
eNodeB correctly.
Criteria
The eNodeB can be adaptive to the PDCCH format
according to the channel condition.
Test result Passed.
5.3.2.2 CFI Self-Adaptive Test Specification
For the CFI self-adaptive test Specification, refer to Table 5-4.

Table 5-4 CFI Self-Adaptive Test Specification
Test item CFI self-adaptive function test.

Verify that the CFI self-adaptive function can be used
Purpose
normally.
Prerequisites 2. The system bandwidth is 20MHz.
3. Multiple UEs are available and they operate properly.
The parameter is set successfully
Set the CFI selection parameter
1 and it is synchronized to the test
to Auto-Adjusted.
eNodeB.
Move the UE to a position near to
The UE is attached to cell
2 the eNodeB and perform the
successfully.
attach operation.
Check the value of the CFI on the
Initiate an FTP download service
3 PCFICH channel delivered by the
for the UE.
eNodeB.
Connect multiple UEs to the Check the value of the CFI on the
4 system and initiate FTP PCFICH channel delivered by the
download services for them. eNodeB.
With the increase of the number of UEs and throughput, the
Expected
value of the CFI changes.
result
With the increase of the number of UEs and throughput, the

Criteria
value of the CFI changes.
Test result Passed.
5.3.3 Test Result
 PDCCH aggregation self-adaptive function:
Save the UE log and open the 0xB130 LTE LL1 PDCCH Decoding Results. Record
the downlink control channel aggregation information. During the test, initiate an FTP
service on the UE and move the UE from cell center to cell edge. The aggregation
increases, see Figure 5-10 and Figure 5-11.
Based on the result, the PDCCH self-adaptive function can be used normally.
 CFI Self-adaptive:
The CFI self-adaptive condition is displayed in the CFI scheduling statistics on the
eNodeB side. For statistic tasks on eNodeB, see the figure below...
Figure 5-12 eNodeB CFI Statistics
According to the test specification, when a UE is connected to the system, the CFI
scheduling condition is changed, see the figure below...
Figure 5-13 CFI Scheduling when a UE is Connected

When two UEs are attached and these two UEs initiated services. For the CFI
scheduling condition, see the figure below...
Figure 5-14 CFI Scheduling when Two UEs are Attached and Initiated Services
When these two UEs terminate the services, for the CFI scheduling condition, see
Figure 5-15.
Figure 5-15 CFI Scheduling when Services are Terminated
Based on the above results, the CFI self-adaptive function can be used normally.
5.4 Adaptive DL MIMO Modes Function
For the verification of self-adaptive MIMO, refer to the LTE FDD Downlink MIMO
Feature Guide.
5.5 Uplink and Downlink Frequency Selection Function
5.5.1 Topology
For the test environment, see the figure below...

Figure 5-16 Uplink and Downlink Frequency Selection Test
For the required devices, refer to Table 5-5.
Table 5-5 Required Devices for the Uplink and Downlink Frequency Selection Function
SN Device Remarks
1 eNodeB One.
2 UE One.
3 Signal source One. It is used to generate
AWGN interference signals.
4 MME One.
5 PDN server One.
5.5.2.1 Uplink Frequency Selection Function Test
For the uplink frequency selection test specification, refer to Table 5-6.
Table 5-6 Uplink Frequency Selection Function Test Specification
Test item Uplink frequency selection function test.

Verify that the uplink frequency selection function can be used
Purpose
normally.
1. Set Maximum RBs Allocated for Uplink UE to 16 and set The
Switch of SRS Configuration to Open [1].
Prerequisites
2. The system works properly and the cell is established
successfully.
Step Expected result
Place the UE to the center of the
The UE is connected to the serving
1 serving cell and perform the attach
cell successfully.
operation.
Initiate an uplink FTP service on the
2 The traffic is in normal status.
UE.
Use the signal resource to generate
The traffic is reduced compared with
3 AWGN noise at the lower frequency
that before noise is added.
of the serving cell.
Stop the uplink FTP, detach the UE,
and configure Uplink Frequency
The parameter is configured
4 Selection parameter to RB Location
successfully.
Sub-Band Allocation (Frequency
Selective).
The uplink traffic is in normal status,
Attach the UE and initiate an uplink
5 and the traffic is not less than that
FTP service.
before noise is added.
After frequency selection is enabled, noise does not affect the
Expected result
throughput.
If the frequency selection is not enabled, the traffic is reduced
Criteria because of noise.
If frequency selection is enabled, noise does not affect the traffic.
Test result Passed.
5.5.2.2 Downlink Frequency Selection Function Test
For the downlink frequency selection test specification, refer to Table 5-7.
Table 5-7 Downlink Frequency Selection Function Test Specification
Test item Downlink frequency selection function test.

Verify that the downlink frequency selection function can
Purpose
be used normally.
1. Set Maximum RBs Allocated for Downlink UE to 16
and set The Method of Feedbacking CQI for PUSCH to
Prerequisites Higher Layer-Configured Subband Feedback.
successfully.
Step Expected result
The UE is attached to the serving
1 serving cell and perform the
cell successfully.
attach operation.
Initiate a downlink FTP service
2 The downlink traffic is properly.
on the UE.
Use the signal resource to
generate AWGN noise at the The traffic is reduced compared
3
lower frequency of the serving with that before noise is added.
cell.
Stop the downlink service,
detach the UE, and configure
Downlink Frequency Selection The parameter is configured
4 to RB Location Sub-Band successfully.
Allocation (Frequency-
Selective).
The downlink traffic is in normal

Attach the UE and initiate
5 status, and the traffic is not less
downlink FTP service.
than that before noise is added.
Expected After frequency selection is enabled, noise does not affect
result the throughput.
If the frequency selection is not enabled, the traffic is
reduced because of noise.
Criteria
If frequency selection is enabled, noise does not affect the
traffic.
Test result Passed.
5.5.3 Test Result
 Uplink frequency selection:
When uplink frequency selection is disabled and noise is not added, the upload traffic
is in normal status, see the figure below...
Figure 5-17 Uplink Frequency Selection Disabled, Noise not Added
When uplink frequency selection is disabled but noise is added, the traffic is affected,
see the figure below.
Figure 5-18 Uplink Frequency Selection Disabled, Noise Added
When uplink frequency selection is enabled and noise is added, the traffic is not
affected, see the figure below.
Figure 5-19 Uplink Frequency Selection Enabled, Noise Added
From the above results, if frequency selection is enabled, the traffic restores to the
normal status.
 Downlink frequency selection:
When downlink frequency selection is disabled and noise is not added, the download
traffic is in normal status, see the figure below...
Figure 5-20 Downlink Frequency Selection Disabled, Noise not Added

When downlink frequency selection is disabled but noise is added, the traffic is
affected, see the figure below.
Figure 5-21 Downlink Frequency Selection Disabled, Noise Added
When downlink frequency selection is enabled and noise is added, the traffic is not
affected, see the figure below...
Figure 5-22 Downlink Frequency Selection Enabled, Noise Added
From the above results, if frequency selection is enabled, the traffic restores to the
normal status.
5.6 UL TTI Bundling
5.6.1 Topology
For the UL TTI Bundling test specification, refer to Table 5-8.

Table 5-8 UL TTI Bundling Test Specification
Test item UL TTI Bundling function test.

Verify that the uplink TTI Bundling function can be used
Purpose
normally.
successfully.
Prerequisites 2. Set Switch of TTI Bundling to Open[1], Open TTI Bundling
SINR Threshold to 4dB, and Close TTI Bundling SINR
Threshold to 8dB.

The UE attaches to the serving cell
successfully.
attach operation.
2 Initiate an uplink UDP service. The traffic is in normal status.
The UE receives the
RRCConnectionReconfiguration
Move the UE to the edge of the message. The ttiBundling field in
cell, making the UE SINR less the MAC-MainConfig IE is TRUE,
3 than Open TTI Bundling SINR which indicates that the UE has
enabled the TTI Bundling function.
Threshold.
The same uplink transmission
blocks are transmitted by
consecutive four uplink sub-frames.
The UE receives the
RRCConnectionReconfiguration
message. The ttiBundling field in
Move the UE from the edge of the MAC-MainConfig IE is FALSE,
the cell to the center of the cell, which indicates that the UE has
4 making the UE SINR greater disabled the TTI Bundling function.
than Close TTI Bundling SINR The uplink scheduling policy is
Threshold. dynamically, which means that
uplink transmission blocks in
subframe n+4 are based on the
received DCI0 in subfram n.
The UE can enable and disable the TTI Bundling function.
Expected When the TTI Bundling function is enabled, the same
result upload transmission blocks are transmitted by consecutive
four uplink sub-frames. When the function is disabled,
dynamic scheduling is used.
The UE can enable and disable the TTI Bundling function.
When the TTI Bundling function is enabled, the same
Criteria upload transmission blocks are transmitted by consecutive
four uplink sub-frames. When the function is disabled,
dynamic scheduling is used.
Test result Passed.
5.6.3 Test Result
After the UE is connected to the system, whether the TTI bundling function is
supported can be checked in the UE's capability message, see Figure 5-23.
Figure 5-23 Checking Whether the TTI bundling Function is Supported
In the initiate status, sub-frames are scheduled independently for PUSCH

scheduling, see the figure below...
Figure 5-24 Sub-Frames Scheduled Independently before the TTI Bundling Function is
Enabled
When the UE is moved to the edge of the cell and the SINR is less than the threshold
for enabling the TTI bundling function, the system delivers the RRC Connection
Reconfiguration message to enable the TTI Bundling function, see the figure below...
Figure 5-25 Enabling the TTI Bundling Function
The information of the consecutive four uploaded sub-frames is the same, see the
figure below.
Figure 5-26 Sub-Frame Scheduling after TTI bundling enabled

When the UE is moved close to the center of cell, and the SINR is greater than the
threshold for disabling the TTI bundling function, the system delivers the RRC
Connection Reconfiguration message to disable the TTI Bundling function, see the
figure below.
Figure 5-27 Disabling the TTI Bundling Function
The scheduling information of the uplink sub-frames are different, see the figure
below.
Figure 5-28 Sub-Frame Scheduling after TTI bundling is not enabled
Based on the results, the TTI bundling function can be used normally.
5.7 Long DRX Function
5.7.1 Topology
For the Long DRX function test specification, refer to Table 5-9.
Table 5-9 Long DRX Function Test
Test item Long DRX function test.

Purpose Verify that the long DRX function can be used normally.
successfully.
2.UE works normally and supports Long DRX function;
3.Test tools of eNodeB side and UE side are available;
4. Main parameter configuration is listed as follow:
Parameter Name Value Unit
E-UTRAN FDD Cell
DRX Switch for GBR Open[1] N/A
DRX Switch for NGBR Open[1] N/A
Service DRX
Prerequisites
Service DRX ID 16 N/A
Label Number of Service
9 N/A
Class
Short DRX Cycle
Yes[1] N/A
Configuration Indicator
Long DRX Cycle 640[7] sf
Short DRX Cycle 40[7] sf
On Duration Timer 20[8] psf
DRX Inactivity Timer 40[10] psf
DRX Retransmission Timer 6[3] psf
Others Default value N/A

successfully.
attach operation.
The traffic is in normal status.
Initiate a downlink UDP service The start and end time of the long
2
with the rate of 500 Kbps. DRX cycle are correct.
The long DRX information can be seen from RRC

Expected Connection Reconfiguration message at the UE side;
result
For NGBR services, the start and end time of the longDRX
Criteria
cycle are correct and the traffic is in normal status.
Test result Passed.
5.7.3 Test Result
For this test, a Qualcomm terminal is used. Check four logs:
Log 0xB198 LTE ML1 CDRX Events Info displays the status information of DRX.
Log 0xB16B LTE PDCCH-PHICH Indication Report displays the PDCCH detection
information.
Log 0xB16D LTE GM TX Report displays the SR and sending of uplink data. Log
0xB173 LTE PDSCH Stat Indication displays the CRC result of downlink PDSCH.
Obversation 1:
First check whether the start and end time of the longDRX cycle are correct, see
Figure 5-29.
Figure 5-29 Start and End Time of the long DRX Cycle
From this figure, the end time of the last DRX cycle, the start time of this DRX cycle
and the time for starting onDurationTimer are the same, and they comply with the
following calculation of the drxStartOffset.
drxStartOffset=[(SFN * 10) + subframe number] modulo (longDRX-Cycle)

=(222*10+9)mod640=309
drxStartOffset is calculated and configured by an upper layer. It is configured in the

RRC signaling message.
For the end time of this DRX cycle, see the figure below...
Figure 5-30 End Time of This DRX Cycle
The start time minus the end time is equal to the cycle of long DRX (2869-
2229=640ms), which complies with the configuration.
Obversation 2:
For the end time of onDurationTimer, see the figure below...
Figure 5-31 End Time of onDurationTimer
END-START=2249-2229=20ms, which complies with the configuration of

onDurationTimer.
Obversation 3:
The closest PDCCH being sent after onDurationTimer is started is 223 3. The
corresponding drx-InactivityTimer has a 3 ms delay, so it is 223 6, which complies
with the expectation. In addition, another PDCCH is detected at 224 4. In this period,
drx-InactivityTimer is still running (2244-2236=8ms<40ms). drx-InactivityTimer is
restarted at 224 6 .
Figure 5-32 Closest PDCCH Sent at Frame 223 Sub-Frame 3 After onDurationTimer is
Started
Figure 5-33 UE Receives the PDCCH Message at Frame 224 Sub-Frame 4
Figure 5-34 Time When drx-InactivityTimer is Started
Observation 4:
The drx-InactivityTimer expires. At 224 9, onDurationTimer expires. After this, the
DRX period is started. At 225 6, drx-InactivityTimer is started. From the PDCCH
messages, we can find that a PDCCH message is received at 225 3 (see Figure 5-
35). Afterwards, no PDCCH message is received until 229 3. This is exactly the
period for the drx-InactivityTimer to expire (see Figure 5-36), which complies with the
expectation. Because onDurationTimer and Drx-RetransmissionTimer stopped, this
complies with the condition for transferring the UE from the active status to the sleep
status. When the UE is in the sleep status, PDCCH is not detected until the next
DRX cycle starts, and onDurationTimer is restarted.
Figure 5-35 drx-InactivityTimer Expires
Figure 5-36 Time When the UE Receives the Final PDCCH
After the UE stays in the sleep status for a while, it enters active status at 231 8 (see
Figure 5-37). This is because at 232 0, an SR scheduling request is sent (see Figure
5-38). Because DRX is maintained in the MAC, and the SR is sent on the phy, the
status transfer happens earlier. This may be attributed to the UE's internal printing
problem.
Figure 5-37 UE Enters active Status

Figure 5-38 UE Sends an SR Message
Observation 5:
After the UE sends uplink data, it maintains the upload retransmission timer to
guarantee that the possible retransmition DCI0 can be received. From the log in the
UE, after the UE sends upload packets in this TTI, if there is no data to be uploaded
in the next TTI, it starts the UL_RETX_TIMER. After the timer is started, if there is
no data to be uploaded within 16 ms, it stops the timer. If not, it restarts the timer,
see Figure 5-39.
Figure 5-39 Starting UL_RETX_TIMER
Obversation 6:
When the downlink HARQ RTT expires, the Drx-RetransmissionTimer

corresponding to this HARQ is started. This timer is stopped when the downlink
retransmission data of this HARQ is received, see Figure 5-40, Figure 5-41 and
Figure 5-42. When the UE receives data with incorrect CRC at 116 6, the HARQRTT
expires at 117 4, but the UE starts the Drx-RetransmissionTimer at 117 1.
Figure 5-40 CRC Test for PDSCH Data Received by the UE
Figure 5-41 Drx-RetransmissionTimer Started
Figure 5-42 Drx-RetransmissionTimer Stopped
5.8 Short DRX Function
5.8.1 Topology
For the Short DRX function test specification, refer to Table 5-10.
Table 5-10 Short DRX Function Test
Test item Short DRX function test.

Purpose Verify that the Short DRX function can be used normally.
successfully.
2.UE works normally and supports Long DRX function;
3.Test tools of eNodeB side and UE side are available;
4. Main parameter configuration is listed as follow:
Parameter Name Value Unit
E-UTRAN FDD Cell
DRX Switch for GBR Open[1] N/A
DRX Switch for NGBR Open[1] N/A
Service DRX
Prerequisites
Service DRX ID 16 N/A
Label Number of Service
9 N/A
Class
Short DRX Cycle
Yes[1] N/A
Configuration Indicator
Long DRX Cycle 320[9] sf
Short DRX Cycle 40[7] sf
On Duration Timer 20[8] psf
DRX Inactivity Timer 40[10] psf
DRX Retransmission Timer 6[3] psf
Others Default value N/A

successfully.
attach operation.
The traffic is in normal status.
Initiate a downlink UDP service The start and end time of the long
2
with the rate of 500 Kbps. DRX cycle are correct.
The short DRX information can be seen from RRC

Expected Connection Reconfiguration message at the UE side;
result
For NGBR services, the start and end time of the Short DRX
Criteria
cycle are correct and the traffic is in normal status.
Test result Passed.
5.8.3 Test Result
The DRX information can be seen from RRC Connection Reconfiguration message at the
UE side.
Figure 5-43 The DRX information can be seen from RRC Connection Reconfiguration
message
The end time minus the start time is equal to the cycle of long DRX (7265-7225=40ms),
which complies with the configuration.
Figure 5-44 Short DRX Start Time and End Time
5.9 Random Access Function
For the random access function test, refer to ZTE LTE FDD Physical Layer
Procedure Feature Guide.
5.10 SPS Function
5.10.1 Topology
For the test environment, refer to 5.1.1 Topology.
5.10.2.1 Uplink SPS Test
For the uplink SPS function test specification, refer to the table below.
Table 5-11 Uplink SPS Function Test Specification
Test item Uplink SPS function test.
Purpose Verify that the uplink SPS function can be used normally.
successfully.
2. Configure an uplink logical channel and set the Scheduler
Prerequisites
Algorithm parameter in case that the QCI is 1 in the EMLP
record to SPS.
3. The system bandwidth is 20MHz.
successfully.
attach operation.
The bearer is established
successfully.
Establish a dedicated bearer The information of SPS-ConfigUL in
2 whose QCI is 1 cell SPS-Config of the RRC
(MBR=GBR=1Mbps) for the UE. Connection Reconfiguration
message received by the UE is the
same as that configured in the
eNodeB.
The uplink service runs properly.
The uplink scheduling used the
SPS scheduling, which means that
after the UE activates the SPS and
Initiate an uplink UDP service on receives a DCI0 scheduling
3 message, the eNodeB does not
this bearer.
send DCI0 messages any more.
The UE uses the RB information
contained in the DCI0 message to
send uplink data according to the
SPS cycle.
Move the UE to the edge of the
The RNTI used by retransmission is
4 cell to trigger HARQ
SPS-C-RNTI.
retransmission.
The UE receives a new DCI0
message. In this message, TPC is
equal to 0, NDI is equal to 0, and
DMRS is equal to 0. The MCS and
Adjust the channel quality and
5 RB obtained in this message are
trigger SPS reactivation.
different from those in the DCI0
message for initial activation. The
UE sends uplink data periodically at
the new resource position.
After three SPS cycles, deactivate
6 Stop the uplink UDP service. the SPS service. The UE no longer
sends uplink data periodically.
The UE can activate and deactivate the SPS function
successfully.
Expected After the SPS function is enabled, the UE receives a DCI0
result scheduling message; the eNodeB does not send DCI0
messages any more. The UE uses the RB information
contained in the DCI0 message to send uplink data
according to the SPS cycle.
successfully.
After the SPS function is enabled, the UE receives a DCI0
Criteria scheduling message, and the eNodeB does not send DCI0
messages any more. The UE uses the RB information
contained in the DCI0 message to send uplink data
Test result Passed.
5.10.2.2 Downlink SPS Test
For the downlink SPS function test Specification, refer to the table below.
Table 5-12 Downlink SPS Function Test Specification
Test item Downlink SPS function test.
Purpose Verify that the downlink SPS function can be used normally.
successfully.
2. Configure a downlink logical channel and set the
Prerequisites
Scheduler Algorithm parameter in case that the QCI is 1 in
the EMLP record to SPS.
3. The system bandwidth is 20MHz.
successfully.
attach operation.
The bearer is established
successfully.
Establish a dedicated bearer The information of SPS-ConfigUL in
2 whose QCI is 1 cell SPS-Config of the RRC
(MBR=GBR=1Mbps) for the UE. Connection Reconfiguration
message received by the UE is the
same as that configured in the
eNodeB.
The downlink service runs properly.
The downlink scheduling used the
SPS scheduling, which means that
after the UE activates the SPS and
Initiate a downlink UDP service receives a DCI1A scheduling
3 message, the eNodeB does not
on this bearer.
send DCI1A messages any more.
The eNodeB uses the RB
information contained in the DCI1A
message to send downlink data
Move the UE to the edge of the
The RNTI used by retransmission is
4 cell to trigger HARQ
SPS-C-RNTI.
retransmission.
The UE receives a new DCI1A
message. In this message, NDI is
equal to 0. The MCS and RB
Adjust the channel quality and obtained in this message are
5
trigger SPS reactivation. different from those in the DCI0
message for initial activation. The
UE sends uplink data periodically at
the new resource position.
After three SPS cycles, deactivate
6 Stop the downlink UDP service.
the SPS service.
successfully.
Expected After the SPS function is enabled, the UE receives a DCI1A
result scheduling message, and the eNodeB does not send DCI1A
messages any more. The eNodeB uses the RB information
contained in the DCI1A message to send downlink data
successfully.
After the SPS function is enabled, the UE receives a DCI1A
Criteria scheduling message, and the eNodeB does not send DCI1A
messages any more. The eNodeB uses the RB information
contained in the DCI1A message to send downlink data
Test result Passed.
5.10.3 Test Result
5.10.3.1 Checking the Uplink SPS Test Result
After the dedicated bearer is established successfully in case that QCI is equal to 1,
you can check whether the configuration of the SPS function is the same as that on
the eNB side from the traced signaling on the UE. The SPS configuration is carried
in RadioResourceConfigDedicated IE in the RRC Connection Reconfiguration
message.
Figure 5-45 SPS Information Checked in RRC Connection Reconfiguration message
On the UE, capture the Log information, and then use the QCAT to check the
information. The following describes how to verify the activation of the SPS function
by using the entire SPS function procedure. The figure below shows the
authorization information of the data transmitted of the SPS service. The DCI0
message is delivered at 196/3 (in this message, Cyclic shift DMRS=0, NDI=0, and
TPC=0). At 196/7, the first SPS uplink data is sent (the start position of RB is 37 and
the number of RBs is 9).
Figure 5-46 UE Receives the SPS Scheduling Authorization Message

Figure 5-47 UE Sends the Uplink Data for the First Time after Receiving the Scheduling
Message
After the SPS function is enabled successfully, the SPS service data is transmitted
every 20 ms at the same frequency. Therefore, in the log information captured on
the UE, only the PUSCH sends messages. Because the uplink HARQ is
synchronized, the HARQ ID scheduled is also synchronized. This conclusion is
proved by the following data.
Figure 5-48 PUSCH Data sent at the SPS Cycle Point (At an Interval of 20 ms)
When the next cycle (198/7) is started, new transmission is initiated. This time, DCI
0 authorization is not required. The PUSCH tx Report and the frequency are the
same (the start position of RB is 37 and the number RBs is 9).
Figure 5-49 SPS PUSCH Data Sent for the second Time
(Note: The UE sends data at the same frequency domain (Start RB=37, Num of
RB=9) as the last SPS scheduling time (SFN/SF=196/7))
From the above test, the SPS scheduling authorization and cyclical usage comply
with the voice service requirement, which saves the PDCCH signaling costs.
The method to check the result of the SPS reactivation test is the same as the above
procedure. A new DCI0 message is received. In this message, TPC, NDI and DMRS
are equal to 0, and the MCS and RB obtained in this message are different from
those in the DCI0 message for initial activation. The UE uses the new MCS and RB
resources to send PUSCH data periodically at the SPS cycle point.
If the UE does not send PUSCH data periodically at the SPS cycle point, the SPS
function is disabled.
5.10.3.2 Checking the Downlink SPS Test Result
The following describes how to check the test result by using an entire SPS function
procedure.
The UE receives the activation command DCI1A (NDI=0) delivered by the eNodeB
at 704/0, see Figure 5-48. The command is demodulated successfully (CRC Pass).
After four sub-frames, the UE returns an ACK message to the eNodeB. At this time,
the downlink SPS is activated successfully. The eNodeB transmits SPS service data
every 20 ms, see the figure below...
Figure 5-50 UE Receives the DCI1A Message that Activates the Downlink SPS Data
Figure 5-51 UE Receives the DCI1A Scheduling Message that Activates the Downlink SPS
Data
The method to check the result of the downlink SPS reactivation test is as follows:
The eNodeB sends a new DCI1A message to the UE to activate the SPS function.
In this message, NDI is equal to 0, and the MCS and RB obtained in this message
are different from the early ones. After the SPS function is reactivated, the BLER
becomes smaller and the number of MCSs and RBs complies with the channel
quality and service requirements. After the UE receives the new DCI1A message, it
checks the PUSCH periodically at the SPS cycle point.
The method to check the result of the downlink SPS deactivation test is as follows:
After the SPS service is stopped, the downlink SPS function is deactivated after three
SPS cycles. eNodeB sends the deactivation message DCI 1A to the UE, and then
receives the ACK message after 4ms. After this, eNB no longer allocates SPS
resources to this UE periodically. On the UE, you can find the deactivation message
DCI 1A in the log. After this, the UE no longer receives PDSCH data periodically.
5.11 HARQ
5.11.1 Topology
For the test environment, refer to 5.1.1 Topology
For the HARQ function test specification, refer to the table below.
Table 5-13 HARQ Function Test Specification
Test item HARQ function test.
Purpose To verify the function of UL and DL HARQ
1. EUTRAN works normally;
2. EPC works normally;
3. Application server runs normally;
Prerequisites 4. OMC works normally;
5. UE is prepared and works normally;
6. Test tools of eNodeB side and UE side are available;

1 Place UE to the cell center;
Start test tool of eNodeB and
2 Test tools work normally;
UE side to record the test log;
Power on UE and make sure
Cell ID of serving cell can be seen at
3 that the UE camps on the
serving cell; UE side;
Initiate Attach operation from
4 UE access serving cell successfully;
UE side;
Start DL FTP service from UE
Record the maximum, minimum,
5 side and keep for at least
1minuter; and average throughput;
Move UE from cell center to cell The downlink data transfer works
6
edge. properly.
The downlink HARQ is
asynchronous, i.e. eNodeB sends the
data in the sub-frame n, if the UE
Record the log and observe the feedbacks the NACK in the sub-
DCI, Subframe ID, HARQ
frame n+4, and then the eNodeB can
7 process ID about the
retransmission data by the tool retransmit the data in any sub-frame
CNT. after the sub-frame n+4. So the
retransmit data has the same HARQ
process ID with the new transmit
data
Stop the DL FTP service, and
8
start UL FTP service.
The uplink HARQ is synchronous,
i.e. eNodeB receives the data in the
sub-frame n, if the eNodeB sends
Record the log and observe the NACK to UE in the sub-frame n + 4,
DCI, Subframe ID, HARQ
then UE retransmits the data in the
9 process ID and RV about the
retransmission data by the tool sub-frame n + 8. So the same HARQ
CNT. process has the fixed sub-frame
numbers to retransmit data. The
sequence of redundancy versions is
0,2,3,1.
1. The downlink HARQ is asynchronous, i.e. eNodeB
sends the data in the sub-frame n, if the UE feedbacks
the NACK in the sub-frame n+4, and then the eNodeB
can retransmit the data in any sub-frame after the sub-
frame n+4. So the retransmit data has the same HARQ
process ID with the new transmit data.
Expected 2. The uplink HARQ is synchronous, i.e. eNodeB receives
result the data in the sub-frame n, if the eNodeB sends NACK
to UE in the sub-frame n + 4, then UE retransmits the
data in the sub-frame n + 8. So the same HARQ
process has the fixed sub-frame numbers to retransmit
data. The sequence of redundancy versions is 0,2,3,1.
1. The downlink and uplink data transfer normally.

Criteria
Test result Passed.
5.11.3 Test Result
 DL HARQ
See the figure below, the downlink transport blocks of CRC results can be seen in
UE’s log “0xB173 LTE PDSCH Stat Indication”. A downlink transport blocks of CRC
results is Fail in subframe 6090. The HARQ ID is 2, the NDI is1, and the RV is 0.
Look for the follow transport block with HARQ ID 2, the subframe is 6098, the NDI is
1 which is same with the before transport block in subframe 6090. It means the
transport block in subframe 6098 is a retransmit data. The CRC result passed in the
subframe 6098 so this retransmit data is transmitted successfully.
Figure 5-52 DL HARQ Test Result
 UL HARQ
The HARQ feedback of uplink data is transmitted on PHICH, which can be seen in
UE’s log “0xB12C LTE LL1 PHICH Decoding Results”.
See the figure below; there is a NAK in PHICH in subframe 5291, so this uplink data
needs to retransmit in subframe 5295, and the RV is 2. The Re-tx index is Second
in UE’s log “0xB139 LTE LL1 PUSCH Tx Report”.
Figure 5-53 There is a NAK in PHICH in subframe 5291
Figure 5-54 The Retransmitted data transmits on PUSCH

Figure 5-55 The Re-tx index
6 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

7
Reference
[1] ZTE LTE FDD Physical Layer Procedure Feature Description;
[2] 3GPP TS 36.212: "Multiplexing and channel coding";
[3]3GPP TS 36.321: "Medium Access Control (MAC) Protocol specification";

ZTE LTE FDD MAC Feature Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE LTE FDD MAC Feature Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

ZTE LTE FDD MAC Feature Guide

Version Date Author Reviewer Notes

Add the following features:

Figure 2-1 LTE Protocol Stack

Table 1-1 Related Feature List and License Control

This document provides the introduction, technical descriptions, parameter

1.1 Feature Attribute

 For FDD single-mode eNodeB V3.30.20.50 series:

 For GUL multi-mode eNodeB V4.15.10.30 series:

EMS version: V12.15.30

OMMB version: V12.15.30

FDD single-mode V3.30.20.50 corresponds to GUL multi-mode V4.15.10.30, and

Table 1-1 Related Feature List and License Control

No Feature List No. Feature List Name License Control

1.3 Correlation with Other Features

Table 1-2 Correlated with Other Features

Feature Feature Name Required Exclusive Affected

2.1 Architecture of the MAC Layer

Figure 2-1 LTE Protocol Stack

Figure 2-2 Architecture of the MAC Layer

The controller provides Discontinuous Reception (DRX), random access channel

2.2 Scheduling Principles

MAC scheduling is based on UE capabilities. For example, if the UE capability level

Modulation and Coding Scheme (MCS) is determined by the Adaptive Modulation

3GPP specifies Semi-Persistent Scheduling (SPS) for voice services. SPS

For the random access descriptions, refer to section Random Access.

2.2.1 Uplink Scheduling

Figure 2-3 Uplink Scheduling Flow

MSG 2 scheduling authorizes uplink scheduling for MSG 3 transmission.

The SPS scheduling module controls VoIP services in semi-persistent scheduling

The retransmission module controls retransmission through the HARQ process. It

The SR response module receives a Scheduling Request (SR) message from a UE

The RB allocation module allocates PRB positions based on dynamic frequency-

2.2.2 Downlink Scheduling

Figure 2-4 Downlink Scheduling Flow

The BCCH/CCCH/PCCH scheduling module allocates resources for common

The retransmission module manages HARQ process retransmission. The downlink

If a UE needs to transmit MAC Control Elements (CEs), the MAC CE scheduling

The QoS scheduling module generates a scheduling priority based on QoS

The RB allocation module determines the PRB position based on different

 CFI (Control Format Indicator)

Number of OFDM symbols occupied by a Physical Downlink Control Channel (PDCCH)

3.2 Technical Details

3.2.1 Logical Channels and Transport Channels

3.2.1.1 Logical Channels

1. Control Logical Channels

 Broadcast Control Channel (BCCH): downlink channel, used to broadcast system

 Dedicated Control Channel (DCCH): used to transmit uplink or downlink control

3.2.1.2 Transport Channels

1. Downlink Transport Channels

 Broadcast Channel (BCH)

 Downlink Shared Channel (DL-SCH): used to transmit subscriber data or control

2. Uplink Transport Channels

3.2.1.3 Multiplexing and Mapping

3.2.2 Scheduling Policies

The RR algorithm guarantees that subscriber polling in cells is scheduled. The

The RR algorithm involves the following parameters:

2. Probability theory: Each subscriber is scheduled by polling, and the scheduled

The RR algorithm is the scheduling algorithm to best guarantee subscriber

In the RR algorithm, the priority factor FF is described as follows:

3.2.2.2 MAX C/I

The MAX C/I algorithm prioritizes subscribers based on the subscribers’

The Proportional Fairness (PF) algorithm is a compromised scheduling algorithm,