LTEScheduling Feature

LTE eRAN3.
0 Scheduling Feature
Confidential Information of Huawei. No Spreading Without Permission
LTE eRAN3.0 Scheduling Feature
LTE air interface scheduling is the responsibility of the eNodeB, however additional
scheduling and QoS (Quality of Service) handling could take place in the EPC (Evolved
Packet Core).
Typically, the main goal of scheduling is to meet the different users expectations.
Historically the radio interface is the weak link or bottle neck in the overall end-to-end
service. This is typically due to limited physical resources, i.e. limited bandwidth or channels.
The scheduling in previous systems, such as GSM and UMTS, was easier. This was due to
the fact that voice was the main service and required a dedicated channel. As such, the
number of channels (or elements) on the base station limited the number of simultaneous
calls.
The eNodeB implements scheduling at the Medium Access Control (MAC) layer and
provides time-and-frequency resources for uplink and downlink through scheduling. On
the premise of guaranteed Quality of Service (QoS), scheduling aims to transmit data on
the channel with better quality and maximize system throughput by using different
channel qualities among UEs.
Huawei eNodeB supports four scheduling strategies:
Max C/I
Round Robin (RR)
Proportional Fair (PF)
Enhanced Proportional Fair (EPF)
The downlink scheduling strategy is decided by the DlschStrategy parameter, and the
uplink scheduling strategy is decided by the UlschStrategy parameter.
With Max C/I, RR, and PF scheduling strategies, dynamic scheduling is used for all services.
With the EPF scheduling strategy, only the VoIP services use semi-persistent scheduling.
Semi-Persistent Scheduling
Semi-persistent scheduling is introduced to reduce the overhead of control

signaling. Semi-persistent scheduling is a process where one user uses the same
time-and-frequency resources in a specified semi-persistent scheduling period (20
ms in Huawei eNodeB) until they are released. Semi-persistent scheduling is mainly
used for processing services with a constant rate, regular packet arrival, and low
delay requirements, such as the Voice over IP (VoIP). By adopting semi-persistent
scheduling, VoIP services can save the overhead of control signaling and increase
the VoIP capacity.
Dynamic Scheduling
In dynamic scheduling, scheduling is performed every Transmission Time Interval

(TTI) of 1 ms and all the UEs to be scheduled are notified with the scheduling
information through control signaling within this TTI. Dynamic scheduling has no
requirements on the size and arrival time of data packets. Therefore, dynamic
scheduling is applicable for all services.
LTE Default and Dedicated EPS bearers are capable of transporting a large variety of traffic
types between the UE and the PDN. This could range from regular Internet browsing based
on HTTP, through to real time voice services based on RTP. Above table outlines the traffic
types which can potentially be encountered, including detail on the characteristics of the
traffic and its associated QCI (QoS Class Identifier) value.
The QCI is a parameter associated with each EPS bearer which will determine the bearer
level packet forwarding treatment e.g. scheduling weights, admission thresholds, queue
management etc. The QCI value of an EPS bearer will be established during the Default or
Dedicated EPS bearer setup procedure.
The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be
delayed between the UE and the EPC.
Scheduling is a very complicated algorithm that involve a lot of input parameters, as shown
in the above figure.
The signaling required for scheduling downlink resources is firstly dependent on the type
of resources being scheduled. The LTE system defines various DCI (Downlink Control
Information). These enable both downlink and uplink scheduling, as well as linking to
different MIMO and diversity options.
Input of DL scheduler
UE Capability: It specifies eight UE categories and the maximum numbers of bits

and layers that can be transmitted in each TTI for each category
Channel quality indicator: Include CQI, PMI and RI report
HARP feedback: ACK and NACK feedback is another input to the scheduler. The
feedback indicates whether data is successfully transmitted or retransmitted. HARQ
retransmissions implemented by Huawei eNodeBs always have a high scheduling
priority
Control-plane data and IMS signaling
Control plane data get the highest scheduling priority and sufficient scheduling
resources are allocated to common control information in the DL
VoIP service
The VoIP service experiencing semi-persistent scheduling has the highest priority.
Semi-persistent scheduling is used in the talk spurts of the VoIP services.
HARQ retransmission data
Other initial transmission services
Other initial transmission services refer to the initial transmission services of other
QCIs excluding VoIP services
Scheduling of common control information uses QPSK and a low coding rate for reliable
transmission. Resource allocations of type 2 is used to allocate resources to common
control information. In resource allocations of type 2, the allocations are classified into
distributed virtual resource block (DVRB) allocations and localized virtual resource block
(LVRB) allocations. The following describes DVRB allocations and LVRB allocations:
DVRB allocations apply to non-contiguous allocation of resource blocks and

increase the coverage of common information. However, the system resources
occupied by common control information increases, resulting in a decrease in the
UE throughput.
LVRB allocations apply to contiguous allocation of resource blocks and decrease
the amount of system resources occupied by common control information and
therefore increase the UE throughput. However, the coverage of common control
information decreases.
Mechanism:
After Nth TTI initial transmission, feeding back ACK/NACK in N+4 TTI, and schedule
retransmission data within N+8 to N+8+k TTI, if the waiting time is more than k
TTI, then this retransmission is discarded.
The priority between each retransmission data is based on waiting time, longer
waiting time cause higher priority
Because of soft-combine gain in PHY layer, the coding rate can be selected higher
for retransmitting data
1. Eliminate the following UEs that do not need prioritization.
UEs that experience semi-persistent scheduling in the current TTI
UEs that experience HARQ retransmission scheduling in the current TTI
UEs that run out of HARQ process numbers
UEs that enter the measurement gap
UEs that enter the DRX dormant period
UEs that stay out of synchronization and have failed radio links
2. Eliminate services (both non-Guaranteed Bit Rate (GBR) and GBR services) whose rates
have met the guaranteed rates. These services do not need prioritization. The decision of
whether rates meet the guaranteed rate is not made on the GBR services with QCI of 1.
Such GBR services are prioritized directly.
Huawei eNodeB sets the minimum guaranteed rate Min_GBR for non-GBR services.
In downlink scheduling, when the rate of the non-GBR service is greater than
Min_GBR or there is no data to be sent in the buffer, the guaranteed rate of the
non-GBR service is considered to be met. In other cases, the guaranteed rate of the
non-GBR service is considered as not met. The Min_GBR in downlink scheduling is
controlled by the DlMinGbr parameter.
Within the specified time period T, if the rate of the scheduled GBR service is
greater than T * (maximum number of DL-SCH transport block bits received within
a TTI) or there is no data to be sent in the buffer, the guaranteed rate of the GBR
service is considered to be met. In other cases, the guaranteed rate of the GBR
service is considered not to be met.
3. Prioritize the remaining services.
The prioritization of non-GBR services is different from that of GBR services.
Huawei eNodeBs can distinguish between BT and non-BT services using a switch under the
DlSchSwitch parameter. If an eNodeB does not distinguish between BT and non-BT
services, the weight factor in downlink scheduling is determined by the
DlschPriorityFactor parameter.
Related commands:
When a UE is handed over to a target cell, initially, the channel quality is poor and the UE
may not report CQIs timely. Therefore, to guarantee the data transmission performance
during this period, Huawei eNodeB sets a static MCS on the UE until the UE reports CQIs
stably. After this, if the UE reports valid CQIs, the system performs MCS selection
according to the previously mentioned procedure.
If part of resources in the RBs for scheduling are occupied by broadcast or synchronization
signals, the actual code rate in data transmission increases with the same TBS. In this case,
the eNodeB adjusts the MCS according to actual situations.
MCS to TBS mapping table MCS Index

0
1
2
3
4
5
6
7
8
9
.
12
27
28
29~31
Modulation
Order
2
2
2
2
2
2
2
2
2
2
.
..
4
6
6
reserved
TBS Index
0
1
2
3
4
5
6
7
8
9
.
.
11
25
26
In downlink scheduling, prioritization and resource allocation are based on the CQI
reported by the UE. The CQI is a key factor in prioritization in downlink scheduling. A UE
that overestimates the channel quality experiences a rise in its scheduling priority, thus
affecting fairness among UEs. On one hand, after a UE that overestimates the channel
quality is scheduled, the IBLER exceeds the target value, thus leading to more
retransmissions and increased service delay. On the other hand, the underestimation of
UEs on the channel quality leads to a waste of system resources, which further affects the
spectral efficiency of the entire system.
Therefore, if the reported CQI fails to reflect the actual channel condition because of the
following reasons, CQI adjustment is required:
The CQI report period is far greater than the scheduling period, which leads to
deviation between the CQI at the reported time and CQI in scheduling. Therefore,
the CQI adjustment algorithm, based on the ACKs and NACKs to initial
transmissions, should check the deviation between the reported CQI and the actual
channel quality and provides an adjusted CQI for scheduling.
The UE is scheduled according to the reported CQI, and the IBLER target value of
the UE is 10%. In actual system, however, the IBLER target value may reach 20%
to maximize system capacity. In this case, the CQI reported by the UE fails to reflect
the actual channel quality because the IBLER target value of the UE is inconsistent
with that of the eNodeB.
The CQI adjustment algorithm is enabled or disabled using the CqiAdjAlgoSwitch

parameter.
Switch of CQI Adjustment
Example of mapping table

I TBS
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
41
1128
1480
1800
2408
2984
3624
4264
4968
5736
6456
7224
8248
9528
10680
11832
12576
13536
14688
16416
17568
19080
20616
22152
23688
25456
26416
30576
42
1160
1544
1864
2472
2984
3752
4392
5160
5992
6712
7480
8504
9528
10680
12216
12960
13536
15264
16416
18336
19848
21384
22920
24496
25456
26416
30576
43
1192
1544
1928
2536
3112
3752
4584
5352
5992
6712
7480
8760
9912
11064
12216
12960
14112
15264
16992
18336
19848
21384
22920
24496
26416
27376
31704
N PRB
44
1224
1608
1992
2536
3112
3880
4584
5352
6200
6968
7736
8760
9912
11448
12576
13536
14112
15840
17568
19080
20616
22152
23688
25456
26416
28336
32856
45
1256
1608
2024
2600
3240
4008
4776
5544
6200
6968
7992
9144
10296
11448
12960
13536
14688
16416
17568
19080
20616
22920
24496
25456
27376
28336
32856
46
1256
1672
2088
2664
3240
4008
4776
5736
6456
7224
7992
9144
10680
11832
12960
14112
14688
16416
18336
19848
21384
22920
24496
26416
28336
29296
34008
47
1288
1736
2088
2728
3368
4136
4968
5736
6456
7480
8248
9528
10680
12216
13536
14688
15264
16992
18336
20616
22152
23688
25456
27376
28336
29296
35160
48
1320
1736
2152
2792
3496
4264
4968
5992
6712
7480
8504
9528
11064
12216
13536
14688
15840
17568
19080
20616
22152
24496
25456
27376
29296
30576
35160
49
1352
1800
2216
2856
3496
4392
5160
5992
6968
7736
8504
9912
11064
12576
14112
15264
15840
17568
19080
21384
22920
24496
26416
28336
29296
31704
36696
50
1384
1800
2216
2856
3624
4392
5160
6200
6968
7992
8760
9912
11448
12960
14112
15264
16416
18336
19848
21384
22920
25456
27376
28336
30576
31704
36696
Uplink scheduling selects an appropriate UE at a proper time and allocates appropriate

resources on the PUSCH to the UE.
After the scheduling request from the UE is received, uplink scheduling is performed on the
UE, and MCS selection and RB allocation are performed on the basis of the current channel
quality of the UE, amount of data to be scheduled, and power headroom. In uplink
scheduling, the channel quality of the UE is indicated by the SINR measured at the physical
layer of the eNodeB. The amount of data to be scheduled depends on the Buffer Status
Report (BSR) reported by the UE. The power headroom depends on the Power Headroom
Report (PHR) reported by the UE.
If TTI bundling and UL semi-persistent scheduling are enabled, the UL scheduler reserves
resources for the two functions, and then allocates resources for UL synchronous nonadaptive HARQ, transmission of message 3, and the control plane. Moreover, if PUSCH
resources are still available, the scheduler allocates resources for SRs reported by UEs and
schedules UEs with unsatisfied GBR and UEs with unsatisfied AMBR.
By using TTI bundling, a TB is transmitted over consecutive subframes and the TTI bundle is
treated as one resource unit to achieve HARQ combining gains in the UL. When the UE
channel quality is poor or the TX power is limited, this feature can be used to improve UL
edge coverage. TTI bundling is specified by the UlSchSwitch parameter.
If TTI bundling is enabled, the eNodeB adaptively determines whether to use TTI bundling
based on channel conditions. The criterion is that UEs are at the cell edge and require TTI
bundling to increase UL edge coverage. The MCS and number of RBs used for TTI bundling
vary according to the channel quality and required data volume. As defined in 3GPP TS
36.213, TTI bundling uses a maximum of three RBs and adopts QPSK as the MCS with the
highest order of 10.
Huawei eNodeB supports UL synchronous non-adaptive HARQ and synchronous adaptive

HARQ.
In synchronous non-adaptive HARQ, the RB positions and MCS for retransmissions are
identical to those for the initial transmission. If the RB positions conflict with PRACH and
PUCCH resources, the retransmission is suspended, affecting the UL throughput.
In synchronous adaptive HARQ, eNodeB adaptively adjust the MCS and RB allocation.
In semi-synchronous adaptive HARQ, eNodeB only adaptively adjust MCS and RB allocation
once data to be retransmitted is allocated resources that conflict with other UL resources
Huawei eNodeB also supports automatic switching between the adaptive and nonadaptive modes. Operators can specify the retransmission mode by the
AdaptHarqSwitch parameter. The automatic switching between the two modes is used
by default.
HARQ adaptive switch
SINR Adjustment: SINR adjustment is specified by the parameter. Due to the impact of
channel fading on signals for moving UEs, the SINR at thUlSchSwitche measurement time
changes significantly, compared with that at the scheduling time. Therefore, it is
recommended that SINR adjustment be enabled. The eNodeB adjusts the SINR based on
ACKs/NACKs to data from UEs. In this way, SINR measurement errors can be corrected and
the measured IBLER value can converge on the target IBLER value, increasing the system
throughput. The target IBLER value is specified by the SinrAdjustTargetIbler parameter.
The target IBLER value is 10% by default, but it may vary in different scenarios. Therefore,
set the target IBLER value based on site requirements.
Command for MCS offset for UCI
A Huawei scheduler satisfies end-to-end QoS requirements. Different from DL QoS

requirements, UL QoS requirements are satisfied at the eNodeB and altogether by using
related parameters delivered from the eNodeB to UEs.
Token rate indicates the volume of water injected into the bucket and specifies the
required data rate
Token size indicates the volume of water remaining in the bucket and specifies whether
the service rate is satisfied as follows:
If the token size is greater than 0, the service rate is not satisfied and a higher
scheduling priority is required
If the token size is equal to 0, the service rate is satisfied.
If the token size is smaller than 0, the service rate is satisfied in advance. The
scheduling priority can be changed to ensure that the service rate satisfies the QoS
requirements
The differentiation between services with different QCIs is achieved by setting the logical
channel priority. The parameters involved are PrioritisedBitRate,
LogicalChannelPriority. Their settings are delivered from the eNodeB to each UE in a
radio resource control (RRC) signaling message. The priorities of services with different
QCIs can be specified as required.
The logical channel priority can be set to a value in the range of 9 to 16. A larger value
indicates a lower priority
As defined in 3GPP specifications, the prioritized bit rate (PBR) of a logical channel can be
set to a value in the range of {0, 8, 16, 32, 64, 128, 256, infinity} in units of kbyte/s. The
UE scheduler guarantees prioritized bit rates of logical channels in descending order of
logical channel priority.
Related command
Based on UL loads, the eNodeB can perform preallocation to reserve resources for UEs
requiring short delays. The preallocation function is controlled by a switch under the
UlSchSwitch parameter. The total resources for preallocation are specified by the
PreAllocationBandwidthRatio parameter that indicates the maximum proportion of the
total RBs available for preallocated UEs in a TTI to the system bandwidth. The amount of
data that can be preallocated to a UE in a preallocation queue is specified by the
PreAllocationSize parameter.
When the preallocation function is enabled, the UEs with unsatisfied AMBR are placed in
the preallocation queue if PUSCH resources are available after the UEs with unsatisfied GBR,
UEs with unsatisfied minimum GBR, and UEs with satisfied minimum GBR but unsatisfied
AMBR are scheduled. The UEs in the preallocation queue must meet the following
requirements:
The UE is not scheduled within the current TTI
The UE meets the minimum interval between preallocations
The UE has a preallocation weight greater than 0
The resource preallocation priorities of UEs in the preallocation queue are determined by
the number of preallocations and the preallocation weight. A smaller number of
preallocations of a UE and a larger preallocation weight indicate a higher priority. If UEs
have the same priority and preallocation weight, the UEs are randomly selected for
preallocation. Preallocation is unavailable for UEs experiencing semi-persistent scheduling
The size of a data packet for a VoIP service has a significant difference in the talk spurts
and silent period. Therefore, the eNodeB determines whether the VoIP service is in the talk
spurts or silent period by checking the size of the data packet. In uplink scheduling, the
eNodeB checks the size of the data packet that is decompressed at the Packet Data
Convergence Protocol (PDCP) layer for the VoIP service. The data packet consists of the
voice frame, Internet Protocol (IP) header, User Datagram Protocol (UDP) header, and RealTime Transport Protocol (RTP) header. In downlink scheduling, the eNodeB checks the
PDCP service data unit (SDU) size of the service before header compression.
Semi-persistent scheduling is fit for VoIP services. It maximizes system capacity while
ensuring speech quality.
In initial scheduling for a service on a UE, an eNodeB indicates the current scheduling
information through the PDCCH. If the UE identifies that semi-persistent scheduling is used,
it saves the scheduling information and then transmits or receives data on constant timefrequency resource positions at fixed intervals. That is, semi-persistent scheduling applies
one grant to periodic data transmissions, based on the characteristic of periodic data
arrival. In this way, a smaller amount of PDCCH resources are required for indicating
scheduling information, and more UEs are served while speech quality and system
performance are maintained.
Parameter description
MO
Parameter
ID
CellAlgo
Switch
CqiAdjAlgoSwitch: Indicates the switch that is used to control

whether to allow the eNodeB to adjust the UE-reported CQI based
on the Initial Block Error Rate (IBLER).
If this switch is set to On, the CQI adjustment algorithm is
enabled. In the case, the eNodeB would adjust the UE-reported
CQI based on the IBLER.
If this switch is set to Off, the CQI adjustment algorithm is
disabled. In this case, the eNodeB would not adjust the UEreported CQI based on the IBLER.
CqiAdjAlgoS
StepVarySwitch: Indicates the switch that is used to enable and
witch
disable the variable-step-based adjustment algorithm.
If this switch is set to On, the variable-step-based adjustment
algorithm is enabled to accelerate the convergence of IBLER. In
this case, rapid adjustment at large steps is applied if there is a
relatively large difference between the measured IBLER and
target IBLER; fine-tuning at small steps is applied if the measured
IBLER approaches the target IBLER.
If this switch is set to Off, the adjustment is performed at a fixed
step.
CellAlgo
Switch
Indicates the switches related to UL scheduling in the cell, which

are used to enable or disable the specific UL scheduling functions.
SpsSchSwitch: Indicates whether to enable or disable semipersistent scheduling during talk spurts of VoIP services.
SinrAdjustSwitch: Indicates whether to adjust the measured SINR
based on ACK/NACK to the UL HARQ process.
PreAllocationSwitch: Indicates whether to enable or disable preallocation, which shortens the end-to-end delay of services when
the UL load is light. If pre-allocation is enabled, the probability of
UEs entering DRX is relatively low and therefore the service time
of the UEs is relatively short.
UlVmimoSwitch: Indicates whether to enable or disable uplink
virtual MIMO. If uplink virtual MIMO is enabled, the eNodeB
selects UEs for pairing according to pairing rules. Then the pair of
UlSchSwitch
UEs transmit data on the same frequency-time resources,
increasing system throughput and spectral efficiency.
TtiBundlingSwitch: Indicates whether to enable or disable TTI
bundling. If TTI bundling is enabled, more transmission
opportunities are available to UEs within the delay budget for VoIP
services on the air interface, improving uplink coverage.
Im2IcSwitch: Indicates whether to enable or disable the secondorder intermodulation (IM2) components elimination for UEs.
During concurrent data transmissions in both UL and DL, two IM2
components are generated symmetrically beside the Direct
Current (DC) subcarrier on the DL receive channel due to the
interference from UL radio signals. If this switch is turned on, IM2
components elimination is performed for UEs. If this switch is
turned off, IM2 components elimination is not performed for UEs.
Description
MO
Parameter
ID
CellAlgo
Switch
Indicates the switch related to DL scheduling in the cell.

FreqSelSwitch: Indicates the switch that is used to control whether
to enable and disable frequency selection and scheduling. If this
switch is set to On, data is transmitted to the UE on the frequency
DlSchSwitch band of good-quality channels.
ServiceDiffSwitch: Indicates the switch that is used to control
whether to enable and disable service differentiation. If this switch
is set to On, service differentiation is applied. If this switch is set to
Off, service differentiation is not applied.
Description
Indicates the switch of the DL scheduling policy. According to the

Max C/I scheduling policy, the UE with good-quality channels are
scheduled and hence the spectral efficiency is very high. The QoS
and fairness among users, however, cannot be ensured. The Max
C/I scheduling policy can be used to verify the maximum capacity
of the system. The RR scheduling policy is the fairest scheduling
policy. When RR is adopted, the smallest system capacity is the
CellDlsch DlschStrateg smallest. Therefore, RR is used only to verify the upper bound of
the scheduling fairness in the system. In terms of the scheduling
Algo
y
effect, the PF scheduling policy is between the previous two
policies. Therefore, PF can be used to verify the capacity,
coverage, and fairness of the system. The EPF scheduling policy
supports the features such as user QoS, system capacity, and
channel frequency selection. The basic scheduling policy is
mainly used for the performance test purpose. During common
operation, the EPF scheduling policy is recommended.
Indicates the weight of the BT service used in EPF scheduling.
The value of this parameter is used in calculating the priority of
the UE during scheduling and therefore determines the amount of
CellDlsch BtServiceWei
physical resources to be allocated to the UE that requests the BT
Algo
ght
service. The BT service priority has a positive correlation with the
value of this parameter. This parameter is valid only when the
service differentiation function is enabled.
Indicates the weight of the non-BT service used in EPF

scheduling. The value of this parameter is used in calculating the
priority of the UE during scheduling and therefore determines the
CellDlsch OtherService amount of resources to be allocated to the UE that requests the
Algo
Weight
non-BT service. The priority of the non-BT service priority has a
positive correlation with the value of this parameter. This
parameter is valid only when the service differentiation function is
enabled.
MO
Parameter
ID
CellUlsch AdaptHarqS
Algo
witch
Description
Indicates the switch that is used to control whether to enable or
disable UL adaptive HARQ. If this switch is set to
ADAPTIVE_HARQ_SW_OFF, UL data is retransmitted by nonadaptive synchronous HARQ. If this switch is set to
ADAPTIVE_HARQ_SW_ON, UL data is retransmitted by adaptive
synchronous HARQ. If this switch is set to
ADAPTIVE_HARQ_SW_SEMION, adaptive HARQ is triggered
when a UL grant is delivered to an HARQ process that is
previously suspended due to reasons such as resource collision,
activation of a measurement gap, and PDCCH congestion. Setting
this parameter to ADAPTIVE_HARQ_SW_ON helps reduce
resource consumption due to retransmission, increase the cell
throughput, and prevent retransmission conflicts. This, on the
other hand, will increase signaling overhead and therefore
consume more PDCCH resources.
Indicates the target IBLER of the SINR adjustment algorithm. A

CellUlsch SinrAdjustTar
greater parameter value indicates a greater SINR adjustment
Algo
getIbler
value, and thus a higher-level MCS is used.
Indicates the priority of the UL user scheduling algorithm and the
policy of arranging the priority of users. According to the Max C/I
scheduling policy, the UEs with good-quality channels are
scheduled, thus the spectral efficiency is very high. The QoS of
and fairness among users, however, cannot be ensured. The Max
C/I scheduling policy can be used to verify the maximum capacity
of the system. The fairest scheduling policy is RR. When RR is
used, the system capacity, however, is the smallest. Therefore,
CellUlsch UlschStrateg
RR is used only to verify the upper limit of the scheduling fairness
Algo
y
in the system. In application effects, the PF scheduling policy is
between the previous two policies. Thus, PF can be used to verify
the capacity, coverage, and fairness of the system. According to
the EPF scheduling policy, the features such as user QoS, system
capacity, and channel frequency selection are considered. The
basic scheduling policy is used during the performance test. In
commercial scenarios, you are advised to use the EPF scheduling
policy.
PreAllocation Indicates the ratio of the maximum bandwidth resources that the
CellUlsch
BandwidthRa uplink scheduler can allocated to pre-allocation users to the total
Algo
tio
system bandwidth.
CellUlsch PreAllocation
Indicates the data amount pre-allocated to each user.
Algo
Size
Indicates the minimum interval between two pre-allocations. That
CellUlsch PreAllocation
is, the actual interval between two pre-allocations of one UE must
Algo
MinPeriod
be longer than or equal to the value of this parameter.
Parameter
ID
MO
Extended
DlMinGbr
QCI
Description
Indicates the downlink minimum guaranteed bit rate of the non-GBR
service.
Extended DlschPriorityF Indicates the weight factor used in the calculation of connection
Qci
actor
priorities during downlink scheduling.
Indicates the priority of the logical channel. The UE scheduler
guarantees prioritized bit rates of logical channels in descending
Extended LogicalChann order of logical channel priority. Resources are allocated in
Qci
elPriority
descending order of logical channel priority after the prioritized bit
rates of all services are guaranteed. For details, see 3GPP TS
36.321.
Extended PrioritisedBit
Qci
Rate
Indicates the prioritized bit rate of the logical channel. The UE

scheduler guarantees prioritized bit rates of logical channels in
descending order of logical channel priority. For details, see 3GPP
TS 36.321.
Extended
UlMinGbr
QCI
Indicates the uplink minimum guaranteed bit rate of the non-GBR

service.
Extended UlschPriorityF Indicates the weight factor used in the calculation of connection
Qci
actor
priorities during uplink scheduling.
Indicates whether to set a logical channel group profile.
GlobalPro
LcgProfile
cSwitch
Currently, two logical channel group profiles are available:

LCG_PROFILE_0 and LCG_PROFILE_1. If LCG_PROFILE_0 is
used, only one logical channel group is assigned to non-GBR
services. If LCG_PROFILE_1 is used, two logical channel groups are
assigned to non-GBR services. One group is assigned to high-priority
non-GBR services, and the other group is assigned to low-priority
non-GBR services.
PUSCHC Qam64Enabl
FG
ed
Indicates whether 64QAM of the PUSCH is enabled. For details, see

3GPP TS 36.211.
Standard
Qci
DlMinGbr
Indicates the downlink minimum guaranteed bit rate of the non-GBR

service.
Standard
Qci
DlschPriorityF Indicates the weight factor used in the calculation of connection

actor
priorities during downlink scheduling.
Standard
Qci
PrioritisedBit
Rate
Indicates the prioritized bit rate of the logical channel. The UE

scheduler guarantees prioritized bit rates of logical channels in
descending order of logical channel priority. For details, see 3GPP
TS 36.321.
MO
Parameter
ID
Standard
UlMinGbr
Qci
Description
Indicates the uplink minimum guaranteed bit rate of the non-GBR
service.
Standard UlschPriority Indicates the weight factor used in the calculation of connection
Qci
Factor
priorities during uplink scheduling.
Indicates the pre-allocation weight. The pre-allocation weight of a
UE is the pre-allocation weight of services carried by the highestpriority logical channel. If services carried by highest-priority
logical channels have different pre-allocation weights, the UE
Standard PreAllocation
takes the highest pre-allocation weight. When resources are
Qci
Weight
insufficient, pre-allocation weights affect the pre-allocation
probabilities of users. The pre-allocation probability has a positive
correlation with the pre-allocation weight. This parameter is QCIspecific.

LTEScheduling Feature

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

LTEScheduling Feature

Transféré par

Droits d'auteur :

Formats disponibles

LTE eRAN3.

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Huawei eNodeB supports four scheduling strategies:

Round Robin (RR)

Proportional Fair (PF)

Enhanced Proportional Fair (EPF)

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Semi-persistent scheduling is introduced to reduce the overhead of control

In dynamic scheduling, scheduling is performed every Transmission Time Interval

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

UE Capability: It specifies eight UE categories and the maximum numbers of bits

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Control-plane data and IMS signaling

HARQ retransmission data

Other initial transmission services

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

DVRB allocations apply to non-contiguous allocation of resource blocks and

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

1. Eliminate the following UEs that do not need prioritization.

UEs that experience semi-persistent scheduling in the current TTI

UEs that experience HARQ retransmission scheduling in the current TTI

UEs that run out of HARQ process numbers

UEs that enter the measurement gap

UEs that enter the DRX dormant period

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

3. Prioritize the remaining services.

The prioritization of non-GBR services is different from that of GBR services.

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN3.0 Scheduling Feature

MCS to TBS mapping table MCS Index