Escolar Documentos
Profissional Documentos
Cultura Documentos
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.2 Test Specification
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.2 Test Specification
5.5.3 Test Result
5.6 UL TTI Bundling
5.6.1 Topology
5.6.2 Test Specification
5.6.3 Test Result
5.7 Long DRX Function
5.7.1 Topology
5.7.2 Test Specification
5.7.3 Test Result
5.8 Short DRX Function
5.8.1 Topology
5.8.2 Test Specification
5.8.3 Test Result
5.9 Random Access Function
5.10 SPS Function
5.10.1 Topology
5.10.2 Test Specification
5.10.3 Test Result
5.11 HARQ
5.11.1 Topology
5.11.2 Test Specification
5.11.3 Test Result
6 Abbreviations
7 Reference
FIGURES
TABLES
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".
EMS: V12.15. 30
OMMB: V12.15.30
Note:
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
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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 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
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.
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.
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 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.
Paging Channel (PCH): used to transmit UE paging messages and notify UEs of system
information update.
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.
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.1 RR
1. Silence duration: Each subscriber shares an equal scheduling opportunity, and thus the
accumulated duration that each subscriber waits for scheduling is identical.
The equation above shows that a longer waiting duration for scheduling results in a
higher scheduling priority.
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.
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
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.
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:
3.2.3 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 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.
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.
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.
The PDCCH indicates the HARQ process ID for initial transmission and
retransmission.
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.
The following four HARQ parameters are important for ZTE eNodeBs although these
parameters are un-modifiable.
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
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.
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.
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).
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.
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.
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
10. Compares the with the number of the remaining RBs in the cell, 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.
16. Compares the with the number of the remaining RBs in the cell, updates
17. Compares the with the number of the remaining RBs in the cell, updates
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.
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.
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.
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.
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.
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.
The MIMO transmission solutions affect the scheduling result. The common
transmission modes include:
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.
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.
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.
Of which,
Key Parameter
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
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.
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;
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 high-correlation environments, that is, RI=1, the following DL transmission modes can
be used:
In the cell center or a good radio environment, where the SINR is good, the following
downlink multi-antenna transmission mode can be used:
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.
For the configuration principle of the downlink multi-antenna transmission mode, see
the following figure:
The current version supports self-adaptive in TM3, TM7, and TM8 modes, between TM3
and TM7 modes, or between TM3 and TM8 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.
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 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.
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.
If the RB obtained by the RB calculating module is less than 1/4 of the system
bandwidth, frequency selection scheduling is not used.
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.
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 2: Determine which type the local cell belongs to according to the relevant calculation
rules, and calculate the initial PRB position of the cell.
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.
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
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.
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:
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.
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.
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.
3.2.9 DRX
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.
– Enabled:
– Disabled:
Enabled:
The uplink or downlink PDCCH with initial transmission is received
Disabled:
Enabled:
Disabled:
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 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.
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.
Random access scheduling includes three scheduling messages: Msg1, Msg2, and
Msg3.
The section only describes the scheduling schemes of random access process.
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).
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.
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.
3.2.11.1 Principle
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.
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.
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.
Downlink SPS is similar to uplink SPS. The difference between them is as follows:
Table 3-2 SPS C-RNTI Configurations for the PDCCH and PDSCH
4 Engineering Guide
None
None
No special requirements
4.3.2 EPC Requirements
No special requirements
No special requirements
4.3.4 UE Requirement
DRX, TTI Bundling and SPS require UE support the corresponding function.
No special requirements
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.
None
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
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 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
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 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
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
2. Click to set QCI1 NI Frequency Select Switch to Both for Newtx and
Retx[2] , see the Figure below.
For downlink frequency selection test, the method of feedbacking the CQI for
PUSCH should be modified as required.
1. In the Configuration Management window, select Modify Area > Radio
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.
3. Click the button.
2. Click to set The Switch of SRS Configuration to Open[1], see the Figure
below.
3. Click the button.
Figure 4-12 Open SRS Feature
2. Click to set Switch of TTI Bundling to Open[1], see the Figure below.
2. Click button, configure the parameters in the figure below according to the
needs.
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.
2. Click to set DRX switch for NGBR to Open[1] and DRX switch for GBR
to Open[1], see the Figure below.
To test the DRX parameter configuration, view or modify the DRX timer parameters:
1. In the Configuration Management window, select Modify Area > Radio
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.
2. Click to set DRX switch for NGBR to Close[0] and DRX switch for GBR
to Close[0], see the Figure below.
The random access feature must be enabled. There is no switch to disable the
feature.
4.4.10 SPS Configuration
5 Function Validation
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
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
For the throughput of UE 2 (far from eNB), see the figure below.
For the throughput of UE 2 (far from eNB), see the figure below...
Figure 5-5 UE 2 Throughput when the 2UE MAX C/I Algorithm is Used
For the throughput of UE 2 (far from eNB), see the figure below...
For the throughput of UE 2 (far from eNB), see the figure below...
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
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.
Figure 5-10 PDCCH Aggregation 1
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...
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-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.
For the verification of self-adaptive MIMO, refer to the LTE FDD Downlink MIMO
Feature Guide.
5.5.1 Topology
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.
For the uplink frequency selection test specification, refer to Table 5-6.
Table 5-6 Uplink Frequency Selection Function Test Specification
For the downlink frequency selection test specification, refer to Table 5-7.
Table 5-7 Downlink Frequency Selection Function Test Specification
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.
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.
When downlink frequency selection is disabled and noise is not added, the download
traffic is in normal status, see the figure below...
When downlink frequency selection is enabled and noise is added, the traffic is not
affected, see the figure below...
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
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-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...
The information of the consecutive four uploaded sub-frames is the same, see the
figure below.
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.1 Topology
For the Long DRX function test specification, refer to Table 5-9.
Table 5-9 Long DRX Function Test
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
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
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.
For the end time of this DRX cycle, see the figure below...
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:
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
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.
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.
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.
Obversation 6:
5.8.1 Topology
For the Short DRX function test specification, refer to Table 5-10.
Table 5-10 Short DRX Function Test
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
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
For the random access function test, refer to ZTE LTE FDD Physical Layer
Procedure Feature Guide.
5.10.1 Topology
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.
Feature ID ZLF31-13-006
Purpose Verify that the uplink SPS function can be used normally.
1. The system works properly and the cell is established
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.
Step Expected step result
Place the UE to the center of the
The UE attaches to the serving cell
1 serving cell and perform the
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.
The UE can activate and deactivate the SPS function
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
according to the SPS cycle.
Test result Passed.
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.
Feature ID ZLF31-13-006
Purpose Verify that the downlink SPS function can be used normally.
1. The system works properly and the cell is established
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.
Step Expected step result
Place the UE to the center of the
The UE attaches to the serving cell
1 serving cell and perform the
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
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 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.
The UE can activate and deactivate the SPS function
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
according to the SPS cycle.
The UE can activate and deactivate the SPS function
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
according to the SPS cycle.
Test result Passed.
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).
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.
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 HARQ function test specification, refer to the table below.
Table 5-13 HARQ Function Test Specification
Test item HARQ function test.
Feature ID ZLF31-13-001
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;
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
6 Abbreviations