1.

1 UL Preallocation
During UL preallocation, eNodeBs proactively send UL scheduling indications to UEs.

1.1.1 Preallocation Mode

Preallocation can work in the following modes:
 normal mode
 smart mode
 voice mode

Figure 1-1 Relationship among the preallocation modes

Normal Preallocation

Normal preallocation is controlled by PreAllocationSwitch of the CellAlgoSwitch.UlSchSwitch

parameter.
During normal preallocation, the preallocation duration is not controllable and preallocation cannot be
performed in DRX mode.
Smart Preallocation

Smart preallocation is controlled by both PreAllocationSwitch and SmartPreAllocationSwitch of the

CellAlgoSwitch.UlSchSwitch parameter.
Smart preallocation is triggered by DL services and cannot be performed before UL TCP services start,
such as web browsing. Therefore, smart preallocation increases the service start delay. Throughput when
smart preallocation is enabled is slightly less than that when normal preallocation is enabled.
The preallocation duration is specified by the CellUlschAlgo.SmartPreAllocationDuration parameter
and CellUlschAlgo.SmartPreAllocDuraForSparse parameter (specifying the duration of a service with
sparse packets in smart preallocation), and preallocation can be performed in DRX mode.
The duration of sparse packets, such as ping service packets, is determined by the larger one between
the value of the CellUlschAlgo.SmartPreAllocationDuration parameter and the
CellUlschAlgo.SmartPreAllocDuraForSparse parameter.
Smart preallocation is disabled if the CellUlschAlgo.SmartPreAllocationDuration and
CellUlschAlgo.SmartPreAllocDuraForSparse parameters are set to 0, and larger values of the two
parameters result in higher UE power consumption. To strike a tradeoff between network throughput and
UE power consumption and make ping services accurately reflect the packet round-trip delay on live
networks, it is recommended that the CellUlschAlgo.SmartPreAllocationDuration parameter be set to
a small value (such as 50 ms) and the CellUlschAlgo.SmartPreAllocDuraForSparse parameter be set
to a value greater than the interval of ping services (such as 1500 ms).
Voice Preallocation

Voice preallocation is controlled by both PreAllocationSwitch of the CellAlgoSwitch.UlSchSwitch

parameter and RsvdSwPara0_bit30 of the eNBRsvdPara.RsvdSwPara0 parameter.
The voice preallocation duration is set to 20 ms and cannot be changed. For a UE in the DRX state, the
voice preallocation duration is the smaller one between 20 ms and the value of the
DrxParaGroup.DrxInactivityTimer parameter.

Factors Affecting Preallocation

Cell-level preallocation depends on the DRX state of UEs and the preallocation status of UEs configured
with an SPID.
 UEs in the DRX state do not support normal preallocation but support smart preallocation and
voice preallocation.
When DRX is enabled, it is recommended that UL smart preallocation also be enabled to ensure
UL throughput and shorten UL delay. Specially, if SRSCFG.SrsCfgInd is set to False and DRX
is enabled without smart preallocation, UL throughput is decreased noticeably.
 The eNodeB can control the preallocation status of UEs configured with an SPID.
If a UE configured with an SPID does not support the preallocation status, the UE does not
support preallocation.

1.1.2 Parameter Settings for Preallocation

Parameter settings for preallocation can be at the cell or QCI level.
Cell-level Parameter Settings
The parameters of MOs CellAlgoSwitch, CellUlschAlgo, and StandardQci need to be set for
preallocation.
PreAllocationSwitch of the CellAlgoSwitch.UlSchSwitch parameter controls whether to enable
preallocation.
Preallocation, including cell- and QCI-level preallocation, takes effect only when PreAllocationSwitch is
set to ON.

QCI-level Parameter Settings

The parameters of MOs CellStandardQci and CellPreallocGroup need to be set for preallocation.
QCI-level preallocation takes effect only when PreAllocationSwitch of the
CellAlgoSwitch.UlSchSwitch parameter is set to ON.
QCI-level preallocation allows different preallocation parameters for services with QCI 1 to QCI 9, and the
parameter settings comply with the minimum delay principle.
Parameter settings for preallocation can be at the cell or QCI level.

1.1.2.1 Cell-level Preallocation Configurations

The total resources for preallocation are specified by the CellUlschAlgo.PreAllocationBandwidthRatio
parameter. This parameter determines the maximum proportion of the total RBs available for preallocated
UEs in a TTI to the system bandwidth.
The amount of data that can be preallocated to a UE in a preallocation queue is specified by the
CellUlschAlgo.PreAllocationSize parameter.
If the preallocation function is enabled, and PUSCH resources are still available after UEs with unsatisfied
GBR, UEs with unsatisfied Min-GBR, and UEs with satisfied Min-GBR but unsatisfied AMBR are
scheduled, then a UE with unsatisfied AMBR is placed in the preallocation queue provided the following
conditions are met:
 The UE is not scheduled within the current TTI.
 The UE meets the requirement for the minimum interval between preallocations.
The minimum interval between preallocations is specified by the
CellUlschAlgo.PreAllocationMinPeriod parameter. If the interval is 1, UEs can be
preallocated in each TTI. If the interval is 2, UEs can be preallocated once every two TTIs.
 The UE has not undergone semi-persistent scheduling.
 The UE has a preallocation weight greater than 0.
The preallocation weight is specified by the StandardQci.PreAllocationWeight parameter,
which is QCI-specific. The preallocation weight of a UE is determined by the preallocation
weight of the services with the highest-priority QCI.
The resource preallocation priorities of UEs in the preallocation queue are determined by the number of
preallocations and the preallocation weight. A UE with a smaller number of preallocations and a greater
preallocation weight has a higher priority. If UEs have the same priority and preallocation weight, the
eNodeB randomly selects UEs for preallocation.

NOTE:
UL preallocation increases the number of times the eNodeB proactively schedules UEs. This quickens
the response to UE services, but increases PDCCH overheads and prolongs the UL data transmission
duration. As a result, the calculated UL throughput decreases, given an unchanged UL traffic volume. The
UL throughput equals the UL traffic volume divided by the UL data transmission duration. However, the
eNodeB cannot measure the duration when the data packets are buffered on the UE side. Therefore, the
calculated result can be used for reference only and cannot be used for the accurate evaluation of data
rates experienced by users. When the switch of the dynamic adjustment on the number of orthogonal
frequency division multiplexing (OFDM) symbols occupied by the PDCCH is turned on, the ratio of the
OFDM symbols occupied by the PDCCH to the total OFDM symbols is increased.
Compared with normal preallocation, smart preallocation achieves a better tradeoff among system gains,
PDCCH overhead, and UL interference. When a small TCP window is configured on the server, the DL
web browsing rate is sensitive to the UL loopback TCP packet delay. Compared with UL normal
preallocation, UL smart preallocation increases the delay and therefore decreases the DL web browsing
rate. UL smart preallocation also increases the start delay for services initiated by upstream devices.

1.1.2.2 QCI-level Preallocation Configurations

In QCI-level preallocation, preallocation parameter groups are configured based on QCI levels. A
preallocation parameter group includes the configurations of preallocation mode, data volume, minimum
preallocation interval, and preallocation duration. Figure 1-1 shows the association between QCI levels
and preallocation parameter groups. A standard QCI associates with a maximum of one preallocation
parameter group.
Figure 1-2 QCI-level preallocation configurations

Preallocation Procedure

The eNodeB traverses the QCIs of all bearers that have been established on a UE.
 If one or more QCIs are configured with valid values of PreallocationParaGroupId,
The eNodeB preferentially uses QCI-level preallocation configurations for the UE and does not
use cell-level preallocation configurations.
If multiple QCIs are configured with different valid values of PreallocationParaGroupId, the
eNodeB selects preallocation configurations for the UE based on the minimum delay principle.
The specific rules are as follows:
 The eNodeB preferentially uses the configurations for normal preallocation and then smart
preallocation.
 If multiple sets of normal preallocation configurations are available, the minimum
preallocation interval equals the minimum one among the configurations and the data
volume for preallocation equals the maximum one among the configurations.
 If multiple sets of smart preallocation configurations are available, the minimum
preallocation interval equals the minimum one among the configurations, the data volume
 for preallocation equals the maximum one among the configurations, and the smart
preallocation duration equals the maximum one among the configurations.
 If none of QCIs are configured with valid values of PreallocationParaGroupId,
The eNodeB uses cell-level preallocation configurations for the UE.