Nokia Multivendor

Optimization Development
Project
Parameter Analysis Guideline- UE Power Control, Scheduling & Link Adaptation
Hexamatics Servcomm Sdn Bhd
30-09-2017

1 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Parameter Analysis Guideline-
UE Power Control, Scheduling
& Link Adaptation
Hexamatics Servcomm Sdn Bhd
30-09-2017

2 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Features Related to Power Control
• Power Control in Ericsson
• Parameters and Counters
• Link Adaptation

3 © 2017 Nokia
 Scheduling

4 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
 Contents
• Scheduling
• Overview
• Scheduling Details
• Parameters and Counters
• Power Control
• Features Related to Power Control
• Power Control in Huawei
• Parameters and Counters
• Link Adaptation

5 © 2017 Nokia
 Overview

6 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Scheduling
Overview:
To provide efficient resource usage, the LTE concept supports fast scheduling where resources on the shared channels PDSCH and PUSCH are assigned to users and radio bearers on sub-frame basis
according to the users momentary traffic demand, QoS requirements and estimated channel quality.
This task is done by the uplink (UL) and downlink (DL) schedulers, both situated in the eNB. Scheduling is also referred to as Dynamic Resource Allocation (DRA) and is part of the Radio Resource Management
(RRM).
In the downlink, the scheduler may assign a set of resource blocks to a user according to a resource allocation scheme while in the uplink resource blocks assigned to a specific user must be contiguous in
the frequency to preserve the SC-FDMA structure.
Also only a limited set of DFT sizes will be allowed, i.e. multiples of powers of 2, 3 and 5. This further limits the number of RB that can be assigned to a user.
In addition to providing an efficient utilization of the radio resource the scheduler is responsible for ensuring the QoS requirements for the individual logical channels to as large extent as possible. When this
is not possible due to resource limitations the scheduler performs prioritization between users and logical channels according to the QoS requirements.
• In the downlink, where the eNB has immediate access to the transmit buffers of the radio bearers; the scheduler performs the prioritization both between users and different radio bearers of a user.
• In the uplink on the other hand the scheduler only prioritizes between different users based on buffer status reports. The prioritization between different logical channels within one UE will be done in the
UE with assistance from the network.

7 © 2017 Nokia
Scheduling (Contd.)
The smallest time/frequency entity that the scheduler may assign consists of twelve sub-carriers (180 kHz) in the frequency domain and a sub-frame (1ms) in time. This corresponds to two 180kHz × 0.5ms
physical resource blocks that are consecutive in time and is referred to as a Scheduling Block (SB) (refer figure 1 in next page)
In the case of MIMO, the resource allocation is the same for all streams. Channel variations can be exploited for multi-user diversity (i.e. scheduling users in constructive fading) both in time and frequency
domain.

In the downlink, the resources handled by the scheduler per cell are:
• Physical Resource Blocks
• PDCCH Resources
• DL Power (not in this release)
• TX rank
• Baseband module processing capability

In the uplink, the resources handled by the scheduler per cell are:
• Physical Resource Blocks
• Baseband module processing capability
• PUCCH Resources

8 © 2017 Nokia
Scheduling (Contd.)
Below figures show Scheduling Block and the resources handled by Scheduler

Figure 1.1: Scheduling Block Figure 1.2: Resources handled by Scheduler

9 © 2017 Nokia
Scheduling (Contd.)
Scheduling Details:
For every cell in every transmission time interval (1ms), the Scheduler determines the UEs that are assigned resources. Each radio bearer is given a certain scheduling priority, based on algorithms which
take the QCI (QoS Class Identifier) related parameters as input.
A higher scheduling priority gives the radio bearer a higher probability to obtain resources and enables the UE to perform transmission or reception. The allocation of resources is made per UE.
The UE priority is defined as the highest scheduling priority of the radio bearers belonging to the UE, including retransmissions. The UE with the highest priority is selected first for transmission.

The different transmissions are prioritized in the following order:

• DL
• Common channels
• HARQ retransmissions of DCCH
• Initial transmissions of DCCH
• HARQ retransmissions of DTCH
• Initial transmissions of DTCH

• UL
• Transmissions of random access msg 3
• HARQ retransmissions
• Initial transmissions of DCCH
• Initial transmissions of DTCH

Figure 1.3: Scheduler Control

10 © 2017 Nokia
Scheduling (Contd.)
Capacity:
The downlink and uplink scheduling algorithms distribute and use the RAN resources dynamically and automatically.
The configurable amount of PUCCH resources for scheduling request and CQI enables the operator to balance the number of supported users with uplink peak throughput.
The scheduling strategies currently available are shown in below table:

Scheduling Strategy Description

Resource Fair (Round Robin) Resource Fair gives more fairness to users served, but leads to lower capacity.
Equal Rate Equal rate is the most fair variant of the proportional fair scheduling algorithms. It strives to give users an equal rate.
Proportional Fair High Proportional Fair High is a high fairness variant of the proportional fair scheduling algorithm.
Proportional Fair Medium Proportional Fair Medium is a medium fairness variant of the proportional fair scheduling algorithm.
Proportional Fair Low Proportional Fair Low is a Low fairness variant of the proportional fair scheduling algorithm.
Maximum C/I Maximum C/I is the least fair variant of the proportional fair scheduling algorithm.
FDD only: Delay Based The delay of each UE is considered to prioritize the scheduling of each user
Resource Fair:
Resource fair scheduling, also called round robin, selects (given highest priority) the radio bearer with the largest time since last scheduling grant. This is a simple and robust form of scheduling that works
well for most services.

11 © 2017 Nokia
Scheduling (Contd.)
Round Robin:
Round robin method is used to allocate the radio resources to users, the first user will be served with the whole frequency spectrum for a
specific period of time and then serve the next user for another time period. Start

The previously served user will be placed at the end of the waiting queue to be served again in the next round. The entire new resources
requests will also be placed at the end of the waiting queue. This scheme offers great fairness in radio resource assignment among the
users but with low throughput Schedule the first user
The principal advantage of Round Robin scheduling is the guaranty of fairness for all users. Furthermore Round Robin is easy to implement,
that is the reason why it is usually used by many systems. Since, Round Robin does not take the channel quality information into
consideration; it results in low user throughput. The flowchart of the Round Robin scheduling is shown in Figure 1.4.
Schedule the next user
Minimum Rate Proportional Fair:
which can be applied as one of its five variants (Equal Rate, Proportional Fair High, Proportional Fair Medium, Proportional Fair Low,
Maximum C/I). It provides a trade-off between user fairness and system performance. By prioritizing users experiencing good channel
quality, a higher throughput can be achieved when compared to Resource Fair.
No Have all users Yes
been
schedules?

Figure 1.4: Round Robin Scheduling flowchart

12 © 2017 Nokia
Scheduling (Contd.)
• The operator can configure the number of PUCCH resources for the scheduling request and the Channel Quality Indicator (CQI) to control the trade -off between the number of supported users and the
uplink peak throughput.
• This is done with the two parameters noOfPucchCqiUsers and noOfPucchSrUsers.
• Users can be periodically assigned CQI resources on PUCCH or dynamically on PUSCH. Users that are not assigned SR resources will have to request uplink resources by performing a Random Access.
• An overview of the inputs and outputs of the Scheduler in uplink and downlink is shown in the figure below. Unless otherwise stated, both uplink and downlink scheduling is considered

Figure 1.5: Scheduler Interactions

13 © 2017 Nokia
Scheduling (Contd.)
Downlink scheduling framework:

• At the beginning of each Transmit Time Interval (TTI), the scheduler receives a list of PRBs, available power, PDCCH capacity, and the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols
for user data.
• Provided resources are available, the scheduler then checks the baseband capacity. The UE to be scheduled is also validated to ensure that it is available for receiving data, and it is synchronized.
• If the Low Energy Scheduler Solution (LESS) feature is activated and predefined conditions are satisfied, remaining scheduling procedures can be skipped on that TTI.
• The Scheduler feature then assigns physical resource blocks in the frequency domain, on a subframe/transmission time interval basis as a scheduling element. In the downlink, the physical resource
blocks are assigned from lower frequencies to higher, that is from left to right.
• When the "Inter-Cell Interference Coordination (ICIC) - autonomous resource allocation" feature is activated in downlink, a random selection is made as to where the allocation starts. It is possible to
configure a proportion of the downlink bandwidth to be used by the downlink scheduler using the dlFrequencyAllocationProportion parameter.
• The allocation can start anywhere within the available range, and wraps around if reaching end-of-range. If the downlink ICIC is disabled, the start frequency offset for the allocation can be specified as a
percentage using the dlConfigurableFrequencyStart parameter. Be aware that using only a fraction of the downlink bandwidth could affect peak throughput and capacity negatively.
• Downlink scheduling uses the CQI as channel quality feedback from the UE. The CQI is sent in uplink on PUCCH or PUSCH. PUSCH provides reports with high frequency for each sub-band when there is data
to transmit. PUCCH gives wide band average reports with low frequency to track path loss when there is no data to transmit to the UE.
• The number of CQI users per cell on PUCCH is configurable with the noOfPucchCqiUsers parameter

14 © 2017 Nokia
Scheduling (Contd.)
The figure shows DL Scheduling Mechanism
• UE provides a Channel Quality Report (CQI) based on DL reference symbol measurements
• DL Scheduler assigns resources per RB based on QoS, CQI etc.
• Resource allocation is transmitted in same TTI as data

Figure 1.6: DL Scheduling Mechanism

15 © 2017 Nokia
Scheduling (Contd.)
Uplink scheduling framework:
• Uplink scheduling takes place in the RBS, and resources are assigned per UE.
• The resources not used by the physical signals PUCCH and PRACH are used as scheduling elements for uplink scheduling, so PUCCH and PRACH have absolute priority over other control and user data
channels in the uplink.
• The random access response message on PDSCH contains the grant for random access message 3 (RRC connection request).
• The UE sends a scheduling request on PUCCH to the scheduler to indicate that it has data in the buffer and asks uplink scheduling to start assigning uplink resource blocks to the UE in upcoming sub
frames. When the UE is scheduled in a sub-frame, the uplink scheduler transmits a scheduling grant to the UE, indicating the resource blocks and transport format to use for uplink transmission.
• Uplink grants are produced by the Scheduler feature and sent to the UE on PDCCH.

• FDD only: The uplink scheduler will grant some resources to every UE using normal HARQ operation which is given the possibility to receive a grant in that TTI. UEs configured for TTI Bundling transmit in
four consecutive TTIs after reception of a grant in that TTI.
• TDD only: The uplink scheduler will grant some resources to every UE using normal HARQ operation which is given the possibility to receive a grant in that TTI.
• When the "Inter-Cell Interference Coordination (ICIC) - autonomous resource allocation" feature is activated in uplink, a random selection is made as to the allocation must start at the lower or the upper
part of the spectrum.
• Together with the uplink data, the UE transmits buffer status information to the RBS such that the uplink scheduler knows roughly the amount of data in the UE buffer.
• In cooperation with link adaptation and power control, the uplink scheduler uses this information together with the channel quality information to assign an appropriate number of resource blocks to the
UE in the uplink

16 © 2017 Nokia
Scheduling (Contd.)
Figure 1.7 shows UL Scheduling Mechanism
• UE requests UL transmission via “scheduling request”
• Scheduler assigns initial resources without detailed knowledge of buffer content
• More detailed buffer status report may follow in connection with data
• Either D-SR on PUCCH or RA-SR on RACH

Figure 1.7: UL Scheduling Mechanism

17 © 2017 Nokia
Advanced Differentiation for Resource Fair Scheduling- FAJ 121 4415
Feature Description:
The feature allows the operator to control the number of scheduling opportunities a bearer gets by configuring relative proportions for services using a specific Quality of Service (QoS) Class Indicator (QCI).
The feature provides the specified scheduling opportunity ratio between two bearers created off two Resource Fair QCIs. The number of scheduling opportunities ratio translate to similar throughput ratio
only when full buffer traffic model is used and when the two UEs being measured have similar radio conditions.
For example, let UE 1 have a relative priority of 2 and UE 2 have a relative priority of 3. UE 1 then gets 2/3 times the number of scheduling opportunities of UE 2. UE 2 gets 3/2 times the number of scheduling
opportunities of UE 1.

Feature Operation:
Network Requirement:
The following must be fulfilled at feature activation:
• The QoS-Aware Scheduler feature license must be active.
Conditions:
The following conditions must be respected to get the expected ratios in term of throughputs when using this feature:
• All UEs must have the same radio frequency conditions (for example, the same Signal to Interference and Noise Ratio (SINR), Channel Quality Indicator (CQI), and Rank Indicator (RI) values).
• The bit rate received at the eNodeB for a bearer must be higher than the rate expected for that bearer.
• The cell must be congested. (That is, the Physical Resource Block (PRB) utilization must be at around 90%.).
• It is recommended that the maximum value for the QciProfileOperatorDefined.relativePriority parameter is 600.

18 © 2017 Nokia
Advanced Differentiation for Resource Fair Scheduling- FAJ 121 4415
(Contd.)
Downlink Advanced Differentiation for Resource Fair Scheduling:
QCIs are grouped into a resource fair relative priority group. For a QCI to be part of a relative priority group the following is required:
• QCIs are configured with Resource Fair Scheduling and a Relative Priority, and
• QCIs are configured with either:
• APO set to no override, in this case all QCIs use the default priority level for user data, or
• All QCIs use the same priority and APO set to override. In this case all QCIs use the priority level configured.
Multiple groups can be configured but only one group is supported.

Associated Parameters:

Parameter Description
Defines the bit rate proportion of the QCI in relation to other QCIs
This parameter is ignored if the feature is not enabled.
relativePriority Note: The maximum value recommended is 600.

schedulingAlgorithm = ResourceFair This RPS extension is for the Resource Fair Scheduling algorithm

Prerequisite Features:
prerequisite features to the Advanced Differentiation for Resource Fair Scheduling feature, that is, they must be active prior to introducing the Advanced Differentiation for Resource Fair Scheduling feature.
• QoS-Aware Scheduler - The QoS-Aware Scheduler feature.

19 © 2017 Nokia
Advanced Differentiation for Resource Fair Scheduling- FAJ 121 4415
(Contd.)
Uplink Direction Unsupported:
This feature implements the downlink direction only. Having this feature in only one direction has an impact on the way resources are distributed between the two directions. Downlink direction tends to get a
higher proportion than uplink after enabling this feature. The resource imbalance impacts as follows:
The downlink direction tends to get higher scheduling weights than uplink and therefore is scheduled more often.
Given that the PDCCH resources are shared between uplink and downlink, the downlink direction tends to get a higher share of the resources as a result of being scheduled more often.
Table below shows the example of how to configure RPS for Resource Fair.

QCI # Priority configured Priority used APO Scheduling Algorithm Relative Priority
7 7 Default priority No-override ResFair 800
8 8 Default priority No-override ResFair 400
9 9 Default priority No-override ResFair 200
Effects on the downlink direction:
• A QCI 7 downlink packet waits ¼ the time that a downlink QCI 9 packet waits
• A QCI 7 downlink packet waits ¼ the time that an uplink packet waits (from QCI 7, 8, or 9)
• A QCI 8 downlink packet waits ½ the time that a downlink QCI 9 packet waits
• A QCI 8 downlink packet waits ½ the time that an uplink packet waits (from QCI 7, 8, or 9)
• A QCI 9 downlink packet waits the same amount of time that an uplink packet waits (from QCI 7, 8, or 9)

20 © 2017 Nokia
Advanced Differentiation for Resource Fair Scheduling- FAJ 121 4415
(Contd.)
Effects on the uplink direction:
• An uplink packet, from QCI 7, 8, or 9, waits 4 times the amount of time that a QCI 7 downlink packet waits
• An uplink packet, from QCI 7, 8, or 9, waits 2 times the amount of time that a QCI 8 downlink packet waits
• An uplink packet, from QCI 7, 8, or 9, waits the same amount of time that a QCI 9 downlink packet waits

Counters:
Below lists the counters associated with the feature

Counter Description
Sum of number of downlink active DRBs for each QCI.
A downlink DRB is active if there are buffered downlink data for the DRB.
Associated events:
pmActiveDrbDlSumQci LOCAL_PER_BB_QCI_EVENT
Exists for MO classes:
EUtranCellFDD.pmActiveDrbDlSumQci
EUtranCellTDD.pmActiveDrbDlSumQci
Total volume (PDCP SDU) that has been transferred (acknowledged by the UE) on DRBs in the downlink direction for each QCI.
Associated events:
LOCAL_PER_BB_RB_EVENT
pmPdcpVolDlDrbQci LOCAL_PER_BB_RB_ON_CELL_QCI_LEVEL_EVENT
Exists for MO classes:
EUtranCellFDD.pmPdcpVolDlDrbQci
EUtranCellTDD.pmPdcpVolDlDrbQci

21 © 2017 Nokia
QoS-Aware Scheduler- FAJ 121 0859
Feature Description:
The QoS-Aware Scheduler feature allows configuration of the scheduler on a QCI basis. This can be used to configure absolute priority scheduling for Data Radio Bearers (DRBs) in regard to air interface
resources. It also enables configuration of scheduling algorithms per QCI, given that appropriate scheduler licenses are in place.
Absolute priority for DRBs must be applied conservatively. It is recommended for use for prioritization of QCI1 [Voice over Internet Protocol (VoIP)] and QCI5 (IMS signaling) only. It is not recommended to be
used for non-Guaranteed Bit Rate (GBR) traffic unless it corresponds to infrequent and low-intensity traffic similar to signaling. Any use of absolute priority scheduling for bearers with high-intensity traffic
will potentially lead to dropping of UEs with less prioritized bearers due to undelivered RLC AM status PDUs.
Since the scheduling in uplink is performed per LCG, it is not recommended to mix QCIs with and without absolute priority in the same LCG. Moreover, SRB1 and SRB2 are always allocated to LCG 0; as a result,
any QCI allocated to LCG 0 will in uplink inherit the scheduling settings of absolute priority scheduling assigned to SRB1/2 . It is recommended only to assign QCIs that corresponds to signaling-like traffic to
LCG 0.

Note: Configuration for predefined QCI profiles is also applicable for operator-defined QCIs , if not stated otherwise.

22 © 2017 Nokia
QoS-Aware Scheduler- FAJ 121 0859 (Contd.)
Feature Operation:
Configuration:

Configuration of the QoS-Aware Scheduler feature is done in the following way:

• First, QCIs are assigned priorities using the QciProfilePredefined.priority parameter.
• Absolute priority is enabled on a QCI basis by means of QciProfilePredefined.absPrioOverride.
• The scheduling algorithm is selected on a QCI basis by means QciProfilePredefined.schedulingAlgorithm .
• For QCIs with the QciProfilePredefined.absPrioOverride parameter set to NO_OVERRIDE, Downlink (DL scheduling) maps the DRB to a default priority level lower (less important) than any other DRB
priority.
• For QCIs with the QciProfilePredefined.absPrioOverride parameter set to HI_PRIO_OVERRIDE, Downlink (DL) scheduling considers the QciProfilePredefined.priority parameter of the DRB as given by
the QCI.
• In uplink, scheduling considers LCGs and this affects the way the parameters QciProfilePredefined.absPrioOverride and QciProfilePredefined.priority are handled by the scheduler. QCIs are grouped
into Logical Channel Groups (LCGs) by assigning the QciProfilePredefined.logicalChannelGroupRef parameter to point to a certain instance of LogicalChannelGroup.
• In a LCG where the QCI with the most important priority have the QciProfilePredefined.absPrioOverride parameter set to NO_OVERRIDE, Uplink (UL scheduling) maps the LCG to a default priority level
lower (less important) than any DRB priority.
• In a LCG where the QCI with the most important priority have the QciProfilePredefined.absPrioOverride parameter set to HI_PRIO_OVERRIDE, Uplink (UL scheduling) maps the LCG to the
QciProfilePredefined.priority parameter of the same QCI.
• In a similar way with regard to scheduling algorithm in uplink, the parameter QciProfilePredefined.schedulingAlgorithm that corresponds to the QCI with the most important priority is selected to
represent the scheduling algorithm of the LCG.

23 © 2017 Nokia
QoS-Aware Scheduler- FAJ 121 0859 (Contd.)
• When a QCI is assigned to LCG 0, the scheduler uses a higher priority than for other LCGs. The priority is similar to that used for SRBs.
• Note that the rules above applies per DRB setup to each specific UE, meaning that two UEs using the same LCG can have different priority in uplink (UL scheduling) if they have bearers from different QCIs
configured

24 © 2017 Nokia
QoS-Aware Scheduler- FAJ 121 0859 (Contd.)
Introduced Parameters:
Below parameter is introduced by the feature.
• absPrioOverride indicates if the DRB mapped to the QCI are subject to absolute priority override. This applies to both downlink and uplink.
Counters:
The important counters associated with the QoS-Aware Scheduler feature are listed below:
Counter Description
FDD only: Aggregated DL latency for a measurement period for each QCI
Exists for MO classes:
pmPdcpLatTimeDlQci
EUtranCellFDD.pmPdcpLatTimeDlQci
EUtranCellTDD.pmPdcpLatTimeDlQci
FDD only: Number of samples for DL latency measurements during measurement period or each QCI
Exists for MO classes:
pmPdcpLatPktTransDlQci
EUtranCellFDD.pmPdcpLatPktTransDlQci
EUtranCellTDD.pmPdcpLatPktTransDlQci
FDD only: Aggregated DL RLC delay for a measurement period or each QCI
Exists for MO classes:
pmRlcDelayTimeDlQci
EUtranCellFDD.pmRlcDelayTimeDlQci
EUtranCellTDD.pmRlcDelayTimeDlQci
FDD only: Number of samples for DL RLC delay measurements during a measurement period or each QCI
Exists for MO classes:
pmRlcDelayPktTransDlQci
EUtranCellFDD.pmRlcDelayPktTransDlQci
EUtranCellTDD.pmRlcDelayPktTransDlQci

25 © 2017 Nokia
QoS-Aware Scheduler- FAJ 121 0859 (Contd.)
PM Events:
The important events associated with the QoS Aware Scheduler feature are listed below.

Event Event Parameter Description

INTERNAL_PER_UE_RB_TRAFFIC_REP EVENT_PARAM_PER_DRB_DL_RLC_DELAY • Aggregated time for the DL delay measure in the RLC layer. One sample per RLC SDU sent to
MAC
• The time for each sample is between reception of a packet (PDCP (4) SDU) until the packet is sent
to the MAC layer entity for transmission on the air.
INTERNAL_PER_UE_RB_TRAFFIC_REP EVENT_PARAM_PER_DRB_DL_RLC_DELAY_SAMPL Number of samples to be used in DL MAC delay measure calculations
INTERNAL_PER_UE_RB_TRAFFIC_REP EVENT_PARAM_PER_DRB_LAT_TIME_DL • Aggregated time samples for the DL latency measure
• The time is between reception of a PDCP SDU until the first successful transmission of a MAC
SDU have been transmitted.
INTERNAL_PER_UE_RB_TRAFFIC_REP EVENT_PARAM_PER_DRB_LAT_SAMPL_DL Number of samples to be used in DL latency measure calculations

26 © 2017 Nokia
Parameters Introduced by Scheduling
noOfPucchSrUsers (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: noOfPucchSrUsers
Description: The number of Scheduling Request (SR) resources available on the PUCCH channel. For 1.4 MHz system bandwidth the recommended value is 50.
GUI Value Range: N/A
Actual Value Range : { 0…4000 }
Recommended Value: 160
Feature ID: N/A Feature Name: Scheduler
Guidance Notes: in case of changing the attributes,Cell runs new set-up procedure. All cell-connected UEs are released and connected again.

noOfPucchCqiUsers (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: noOfPucchCqiUsers
Description: The number of Channel Quality Indicator (CQI) resources available on the PUCCH channel. For 1.4 MHz system bandwidth the recommended value is 50
GUI Value Range: N/A
Actual Value Range: { 0…4000 }
Recommended Value: 160
Feature ID: N/A Feature Name: Scheduler
Guidance Notes: in case of changing the attributes,Cell runs new set-up procedure. All cell-connected UEs are released and connected again.

27 © 2017 Nokia
Parameters Introduced by Scheduling (Contd.)
schedulingAlgorithm (MO: ENodeBFunction >> QciProfilePredefined) Impact Area-Accessibility
Parameter Name: schedulingAlgorithm
Description: Specifies which scheduling algorithm is to be used for a certain QCI.
GUI Value Range: N/A
Actual Value Range: RESOURCE_FAIR, EQUAL_RATE, PROPORTIONAL_FAIR_HIGH, PROPORTIONAL_FAIR_MEDIUM, PROPORTIONAL_FAIR_LOW, MAXIMUM_C_OVER_I, DELAY_BASED
Recommended Value: RESOURCE_FAIR
Feature ID: N/A Feature Name: Scheduler
Guidance Notes: Only relevant if the license for QoS Aware Scheduler is present and the feature is active. The value DELAY_BASED can only be used if the attribute serviceType has value VOIP.

28 © 2017 Nokia
Parameters Introduced by Scheduling (Contd.)
pdcchCfiMode (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: pdcchCfiMode
Description: Controls the CFI (Control Format Indicator) used for the control region. cfiMode maps to CFI as described under enumerations. For DL BW of 1400 kHz, values of CFI = 1, 2 and 3 map to 2, 3, and 4
control region symbols respectively. Other BW, CFI maps directly to number of control region symbols.
GUI Value Range: N/A
Actual Value Range: CFI_STATIC_BY_BW
Recommended Value: CFI_STATIC_BY_BW
Feature ID: N/A Feature Name: Scheduler
Guidance Notes: pdcchCfiMode cannot equal CFI_STATIC_1 while dlChannelBandwidth = 1400, 3000, or 5000 kHz since there would be insufficient CCEs to transmit a PDCCH for common channel messages
such as SIB1 or SI. Certain values of pdcchCfiMode that allow high CFI values may be disallowed when the combination of attributes pdcchCfiMode, dlChannelBandwidth, noOfPucchCqiUsers, and
noOfPucchSrUsers require too many corresponding PUCCH HARQ-ARQ resources

29 © 2017 Nokia
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Power Control in Ericsson
• Features Related to Power Control
• Parameters and Counters
• Link Adaptation

30 © 2017 Nokia
 Power Control

31 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Power Control in Ericsson
• Features Related to Power Control
• Parameters and Counters
• Link Adaptation

32 © 2017 Nokia
 Power Control in Ericsson

33 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control
Introduction:
Power control and power configuration reduces inter-cell interference and power consumption. This leads to
higher cell capacity and the control of maximum data rate for a UE at cell edge. In addition, it maximizes
battery life for the UE.
Power Control is used to minimize the transmitted power and to compensate for channel fading. Its objective
is to maximize capacity by optimizing the transmit power.
The Power Control feature can be activated with PDCCH Power Boost feature simultaneously to improve
cell capacity and cell coverage.
Power control regulates the PSD (Power Spectral Density) of the transmitted signal and starts immediately
when enough measurements are collected.
The following types of power control algorithms as described in Figure 1.8 are employed in E-UTRAN.

Figure 1.8: Power Control in LTE

34 © 2017 Nokia
Power Control (Contd.)
The basic feature Adjustable CRS (Cell-specific Reference Signal) Power is enhanced to provide operators the possibility to configure Power of PDSCH type B resource elements.
With this feature, the operator has the possibility to change the power of PDSCH type B resource elements such as the resource elements in OFDM symbols that include reference symbols.

The Power Control feature involves the following functions:

• Power control
• Link adaptation
• Antenna transmission mode control
• Channel prediction

These are all part of the basic LTE functions that reside in the RBS. They use the following channel condition information as input parameters:
• Characteristics of the radio channel
• Quality requirement of the transmitted information
• Power control and power configuration reduce inter-cell interference and power consumption. This leads to higher cell capacity and the control of the maximum data rate for User Equipment (UE) at cell
edge. In addition, it helps to prolong the battery life of the UE

35 © 2017 Nokia
Power Control (Contd.)
The Power Control feature could be activated with PDCCH Power Boost feature simultaneously to improve cell capacity and cell coverage.
The main benefits for an operator are:
• Improved flexibility for tuning and optimization of downlink resource element power allocation
• Improved DL throughput, e.g. in high dense networks.
Adjustable Cell-specific Reference Signal (CRS) power provides means to optimize the power distribution on resource elements according to the network topology for improved DL throughput, for example in
dense networks, or extended coverage in rural environments. More precisely, to be able to tune the network performance and the inter-cell interference there is support for controlling the power of the DL
reference signals.

36 © 2017 Nokia
Power Control (Contd.)
Open loop Power Control:
Open loop power control is used for:
• Regulating power for PRACH at initial access (Random Access)
• Regulating power for PUSCH and PUCCH as part of UL power control

Open loop power control for Random Access:

The aim of initial random access open loop power control in the uplink is to ensure new connections are
established causing minimum interference.
The three basic steps employed are shown in Figure 1.9.

Open Loop Power Control is used in the uplink to minimize uplink interference when setting up a connection.

Figure 1.9: Uplink Open Loop Power Control

37 © 2017 Nokia
Power Control (Contd.)
There are two types of the Random Access preamble groups. Depending on the message size and pathloss UE will select either Random Access Preamble group A or B. Once the group is selected the UE
will randomly select a preamble within the group.
• Once preamble has been selected or it has been given by the network it should be sent using initial power setting
• There are two preamble formats, 0 and 1. Using preamble format 1 makes it possible to increase the cellrange to 100 km. In the current release, both preamble formats 0 and 1 will be supported. Since L12
the rachRootSequence parameter was introduced.
• rachRootSequence takes the value in the range of 0 to 837. The default value is 386.
• It is recommended to set the parameter rachRootSequence to different values in neighboring cells to reduce the probability for false RACH detections. The values must differ by at least 10 between any
two neighbors (and at most 827 since there is a wrap-around between the first and last value in the value.
• Random Access parameters are broadcasted in SIB2.

Figure 2.0: Preamble based Power Ramping

38 © 2017 Nokia
Power Control (Contd.)
DL Power Control:
Common Channel Power Control:
• The power levels for common channels are defined relative to a common Reference PSD; PSD_reference. This PSD_reference, is the PSD available out from the Radio Unit for each RE on each antenna if
the totally available radio unit transmission power is split equally over all Resource Elements in the configured downlink bandwidth and all antennas configured for transmission in the cell.
• 3GPP has specified the modulation, coding and BLER requirements for PBCH, PCFICH, RS and SS so that they all have the same performance at the cell edge when they have the same PSD (Power Spectral
Density) per Resource Element.
• All common and shared downlink channels and signals have the PSD set equal to PSD_reference. However the RS PSD in the case of two, four or eight transmit antenna ports can be controllable via a MOM
parameter crsGain (EUtranCellFDD.crsGain or EUtranCellTDD.crsGain). In these cases, when an RE is used for transmission of RS on any of antenna ports in a subframe, it will not be used for any
transmission on any other antenna port in the same subframe.
• The exception is the RS PSD for the case of two antenna ports. In this case there will be an unused RE on one antenna port when there is an RS on the corresponding RE on the other antenna port. As a
result, there is a 3 dB boost for “free”, i.e. PSDRS will be 2 times PSD_reference. That is because energy can be moved within one power amplifier, between different REs in the same OFDM symbol.

39 © 2017 Nokia
Power Control (Contd.)
UL Power Control:
Uplink power control is used both on the PUSCH and on the PUCCH. In both cases, a parameterized open loop combined with a closed loop mechanism is used. Roughly, the open loop part is used to set a point
of operation, around which the closed loop component operates. Different parameters (targets and 'partial compensation factors') for user and control plane are used.

Figure 2.1: Uplink Power Control

40 © 2017 Nokia
Power Control (Contd.)
PUSCH Power Control:
Power control for PUSCH reduces the PSDTX for UEs close to the RBS. The PSDRX is variant based on path loss when fractional path loss compensation is used (α<1). In this case, cell center UE has higher
PSDRX and cell edge UE has lower PSDRX. If full path loss compensation is used (α=1), the PSDRX is kept constant. The actual PSDTX is used to calculate SINR (based on GINR and PSD), used by PUSCH link
adaptation.
PUSCH power setting equation:

P=min [Pmax, 10logM + P0 + α x PL + ∆mcs + f (∆i)] dBm

Where,
• Pmax is the UE power capability.
• M is the number of scheduled resource blocks.
• α is the path-loss compensation factor, set according to the parameter alpha (EUtranCellFDD.alpha or EUtranCellTDD.alpha) which is the fractional factor compensation for the path loss.
• Po is the target PSDRX for each resource block, set according to the parameter pZeroNominalPusch (EUtranCellFDD.pZeroNominalPusch or EUtranCellTDD.pZeroNominalPusch). Po is common for all
UEs in the cell.
• Δmcs is an MCS-specific offset and set to 0.
• PL is the path loss estimated by the UE.
• The f(Δi) is the closed loop power control part, while the rest is the open loop power control part. Δi is a UE specific power adjustment included in the uplink scheduling grant on PDCCH. The closed loop
power adjustments are used to enforce the open loop PSDRX target in the RBS. It is updated fast enough to follow slow fading.

41 © 2017 Nokia
Power Control (Contd.)
PUCCH Power Control:
PUCCH is power controlled independently via an open loop and a closed loop with Transmission Power Control (TPC) commands transmitted on PDCCH. The power setting formula for PUCCH is as follows:

Ppucch [i] =min [Pmax, P0pucch + PL + h (ncqi, nharq) + ∆Fpucch (F) + g (i)] dBm
Where,
• Pmax is the UE power capability.
• P0pucch is the target PSDRX for PUCCH, corresponding to Po for PUSCH. It is set according to the parameter pZeroNominalPucch and signaled separately on BCCH System Information Blocks (SIBs).
• PL is the pathless estimate and is the same as for PUSCH.
• h(n) is a PUCCH format dependent value where ncqi corresponds to the number of information bits for the CQI, and nharq the number of HARQ bits.
• ΔF,pucch is an offset that depends on the information transmitted on PUCCH.
• g(i) is the current PUCCH power control adjustment state.
• The open loop part controls P0pucch, and the closed loop part controls g(i).

42 © 2017 Nokia
Power Control (Contd.)
Link adaptation (LA) selects the transport format to ensure that the quality of service requirements are enforced while using resources efficiently. It is also essential for maximizing user throughput over
the air interface.
Channel prediction provides information needed for determining functions such as changing power and the modulation scheme. This comes from UE measurements in Channel Feedback Reports (CFRs). The
resulting data rate also depends on scheduling the Physical Resource Blocks (PRBs).

Figure 2.2: Scheduling, LA and PC Summary

43 © 2017 Nokia
Power Control (Contd.)
• A QCI is a scalar that is used as a reference to access node specific parameters that control bearer level packet treatment (e.g. scheduling behavior, queue management thresholds, link layer protocol
configurations etc.).
• DRA – Dynamic Resource Allocation is another name for Scheduling.
• CFR – Channel Feedback Report consist of CQI, PMI and RI
• CQI – Channel Quality Indicator is an index that is communicated to the eNB that indicates link adaptation parameters. Code rate is the ratio between the data bits and (the data bits + redundancy).
Efficiency is the effective number of bits per symbol.

CQI Index Modulation Code rate x1024 Efficiency CQI Index Modulation Code rate x 1024 Efficiency

0 Out of range 8 16QAM 490 1.9141

1 QPSK 78 0.1523 9 16QAM 616 2.4063
2 QPSK 120 0.2344 10 64QAM 466 2.7305
3 QPSK 193 0.3770 11 64QAM 567 3.3223
4 QPSK 308 0.6016 12 64QAM 666 3.9023
5 QPSK 449 0.8770 13 64QAM 772 4.5234
6 QPSK 602 1.1758 14 64QAM 873 5.1152
7 16QAM 378 1.4766 15 64QAM 948 5.5547

Figure 2.3: CQI Mapping

44 © 2017 Nokia
Power Control (Contd.)
Power Headroom Report
Power Headroom Report MAC control element tells if UE can transmit at a higher transmission power or not. In basic terms this indicates how much relative transmission power left in the UE.
A simple formula for Power Headroom in LTE is as follows:

Power Headroom = UE Max Transmission Power – PUSCH Power = Pmax – P_pusch

So if Power Headroom is a positive value, that means UE is still capable to send at higher Tx power or it is capable of transmitting at higher throughput. If the value is negative, UE is already transmitting at
maximum Tx power.
In the positive Power Headroom case, network may allocate more resource blocks to the UE, but in the negative Power Headroom case it is assumed that UE is already using the maximum resource blocks
and no need to assign more.

Power Headroom Report Control Element:

Power Headroom Report MAC control element is of single octet long. It has three field with the two left most bits reserved. The rightmost 6 bits are defined as PH field.

Note: The reported power headroom shall be estimated over 1 subframe. The power headroom shall be estimated only in a subframe where PUSCH is transmitted

45 © 2017 Nokia
Power Control (Contd.)
Power Headroom Levels for PHR:
PH of Power headroom field corresponds to the power headroom level defined in the following table in Figure 2.9.

Power Headroom Report Mapping:

The power headroom reporting range is from -23 …+40 dB as shown in Figure 3.0.

Figure 2.4a: Power Headroom levels for PHR

Figure 32.4b Power report mapping

46 © 2017 Nokia
Power Control (Contd.)
There are two ways this can be configured in the UE through RRC messages:
• When downlink pathloss threshold is reached (dl-PathlossChange)
• When periodicPHR-Timer is set, UE send periodically the Power Headroom Report to the network
Check for RRC messages like RRC Connection Setup, RRC Connection Reconfiguration to get the details of the Power Headroom
configuration used. Search for IE phr-Config.

RRCConnectionReconfiguration Message:
• dl-PathlossChange: DL Pathloss Change and the change of the required power backoff due to power management. Value in dB.
Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on.
• periodicPHR-Timer: Timer for PHR reporting. Value in number of sub-frames. Value sf10 corresponds to 10 subframes, sf20
corresponds to 20 subframes and so on.
• prohibitPHR-Timer: Timer for PHR reporting. Specifies, how long PHR transmission is prohibited. Value in number of sub-frames.
Value sf0 corresponds to 0 subframes, sf100 corresponds to 100 subframes and so on

Figure 2.5: RRCConnectionReconfiguration Message

47 © 2017 Nokia
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Power Control in Ericsson
• Features Related to Power Control
• Parameters and Counters
• Link Adaptation

48 © 2017 Nokia
 Features Related to Power
Control

49 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Features Related to Power Control
Differential Uplink Power Control:

Feature Name Differential Uplink Power Control

Product Identity FAJ 121 4680
Replaces N/A
Dependencies N/A
Licensing Licensed feature. One license required for each node

Feature Summary: Differential Uplink Power Control

• Differential Uplink Power Control introduces a new SINR-based PUSCH closed-loop power control algorithm. This calculates Transmit Power Control (TPC) commands based on the received uplink SINR and
the configured SINR target.
• There are two kinds of PUSCH closed-loop power control algorithms, P0-based and SINR-based. This feature introduces the switching between them, in accordance with cell interference levels and cell
uplink power load. This feature can also mitigate the influence of high external uplink LTE interference by increasing the UE uplink Tx power.
• SINR-based closed-loop power control is introduced to control UE PUSCH transmission power. The operator can configure measurement thresholds for switching between P0- and SINR-based
power control, in accordance with actual network conditions
• With P0-based closed-loop power control, PUSCH transmission power is adjusted to achieve the expected uplink PSD target by TPC command, in which uplink interference is not taken into account
for UE power adjustment.

50 © 2017 Nokia
Features Related to Power Control (Contd.)
• The advantage of SINR-based closed-loop power control is that it takes interference into account when adjusting UE PUSCH power. This is especially useful in the case of wideband and time-variable
external uplink interference. In this case, it is difficult for the operator to set a suitable P0 to fully compensate for time-variable interference. SINR-based closed-loop power control can provide
reasonable SINR for PUSCH reception unless the UE uplink transmission power reaches its maximum

Network Requirements:
This is a licensed feature. This means that for the feature to be operational, a valid license key must be installed and the feature must be explicitly activated by setting a MOM attribute.
Also, the feature must be enabled on cell level using the MO attribute enableSinrUplinkClpc in MO Class EUtranCellFDD or EUtranCellTDD

Parameter Description
enableSinrUplinkClpc
Disable or enable Differential Uplink Power Control feature on cell level. The feature status can be changed without locking and unlocking the cell.

rxSinrTargetClpc PUSCH SINR target value for SINR-based uplink closed-loop power control.
interferenceThresholdSinrClpc Threshold value for measured noise plus interference level. If measured noise plus interference is higher than interferenceThresholdSinrClpc, SINR-based
uplink closed-loop power control can be considered.
ulPsdLoadThresholdSinrClpc Threshold of uplink Tx power for each PRB for estimation of cell uplink power load. If averaged uplink Tx power measurement per PRB is lower than
ulPsdLoadThresholdSinrClpc over a set percentage of uplink bandwidth, SINR-based uplink closed-loop power control can be considered .

ulTxPsdDistrThr Threshold for estimation of cell uplink power load. Cell uplink power load is the percentage of PRBs with uplink Tx power higher than ulPsdLoadThresholdSinrClpc
during measSinrClpcPeriod. If the estimated cell uplink power load is lower than ulTxPsdDistrThr, SINR-based uplink closed-loop power control can be
considered(4).

51 © 2017 Nokia
Features Related to Power Control (Contd.)
Dynamic Random Access Backoff:

Feature Name Dynamic Random Access Backoff

Product Identity FAJ 121 4299
Replaces N/A
Dependencies N/A
Licensing Licensed feature. One license required for each node

Feature Summary: Dynamic Random Access Backoff

• This feature provides support for spreading Random Access (RA) retries over time. This minimizes the probability of simultaneous RA retries, and in that way congestion on the Random Access Channel
(RACH) is avoided.
• The total number of Contention Based Random Access (CBRA) and Contention Free Random Access (CFRA) preambles received in the cell is detected and used to calculate a dynamic backoff value. This
backoff value is sent to UEs performing RA retries in the random access response. The backoff value is chosen dynamically, and is chosen high enough to reduce the risks of failed RA retries. However, it
is also chosen low enough to minimize the latency from the first RA attempt until successful completion of the RA procedure.
• This feature improves robustness by reducing the risk for overload and contention when many UEs try to connect to the eNodeB at the same time.
• The main benefits of the feature are:
• Improved inter-cell interference.
• Improved RA success rate.
• Lower latency for UEs to connect to the eNodeB to reacquire UL synchronization, or request a UL grant using SR-RACH when the load on RA is high.

52 © 2017 Nokia
Features Related to Power Control (Contd.)
Fractional Pathloss Power Control:

Feature Name Fractional Pathloss Power Control

Product Identity FAJ 121 3033
Replaces N/A
Dependencies N/A
Licensing Basic feature. No license is required.

Feature Summary: Fractional Pathloss Power Control

• With fractional pathloss power control, it is easier to set power control parameters that enables UL peak rate in the cell without sacrificing cell-edge performance too much. In addition, trade-off is
possible between average and cell edge throughput. For small data buffers, a lower transmit power at cell edge could result in a lower battery consumption.
• The uplink power control for the shared channel is by default configured so that the target received power spectral density (PSD) at the eNB is constant, regardless of where in the cell the UE is. This is
done in the UE by estimating pathloss (PL) and fully compensating the output power with that estimation. The target received PSD at the eNB is determined by the attribute pZeroNominalPusch.
• With this feature it is possible to configure the power control to partially compensate for pathloss, leading to that the received PSD depends on the pathloss. This gives a larger freedom in how to optimize
uplink power control. For example, it is possible to lower output power for cell-edge UEs (high pathloss) in order to reduce interference spread in the system while still maintaining a high PSD for cell
center user in order to provide best possible peak bitrates.

53 © 2017 Nokia
Features Related to Power Control (Contd.)
PUCCH Overdimensioning:

Feature Name PUCCH Overdimensioning

Product Identity FAJ 121 0883
Replaces N/A
Dependencies N/A
Licensing Basic feature. No license is required.

Feature Summary: PUCCH Overdimensioning:

• PUCCH Overdimensioning is a feature that is used to change the frequency position of the Physical Uplink Control Channel (PUCCH).
• The main benefit of this feature is the capability to support a wide range of different regulatory requirements imposed to different E-UTRAN frequency bands. This is done with maintained PUCCH
performance and coverage
• In specific deployment scenarios where Additional Maximum Power Reduction (A-MPR) restrictions apply, the User Equipment (UE) is allowed to reduce the output power in parts of, or in the full frequency
band. By doing this, interference in neighboring frequency bands is reduced. Since the PUCCH is at the band edges, its performance is degraded if the UE output power is reduced at the band edges. The
PUCCH Overdimensioning feature allows the PUCCH region to be moved to another part of the Uplink (UL) system bandwidth where A-MPR restrictions are less severe. In this way, PUCCH performance
can be secured.
• In the reverse scenario, the transmission in neighboring frequency bands degrades LTE system performance at the band edges. In this scenario, the PUCCH Overdimensioning feature can be used to move
the PUCCH region to frequency regions with less interference from the neighboring bands

Note: It is only recommended to use the PUCCH Overdimensioning feature in the specific deployment scenarios described above. Under normal conditions, no gain is expected from the feature.

54 © 2017 Nokia
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Power Control in Ericsson
• Features Related to Power Control
• Parameters and Counters
• Link Adaptation

55 © 2017 Nokia
 Parameters and Counters

56 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Parameters Introduced by Power Control
maximumTransmissionPower (MO: ENodeBFunction >> SectorCarrier ) Impact Area-Accessibility
Parameter Name: maximumTransmissionPower
Description: Maximum possible power at the antenna reference point, for all downlink channels in all TX branches used simultaneously in the Sector Carrier. -1 is used as an undefined value.
GUI Value Range: N/A
Actual Value Range: { -1…1200 }
Recommended Value: 0
Feature ID: N/A Feature Name: Power Control
Guidance Notes : None

configuredMaxTxPower (MO: ENodeBFunction >> SectorCarrier ) Impact Area-Accessibility

Parameter Name: configuredMaxTxPower
Description: Maximum output power to be used in a Sector Carrier. The output power is evenly distributed over antenna connectors used for TX transmission allocated for the Sector Carrier. Value 0 must
not be used.
To prevent the cell from transmitting, it must be locked
GUI Value Range: N/A
Actual Value Range: { 0...10000000 }
Recommended Value: 20000
Feature ID: N/A Feature Name: Power Control
Guidance Notes: None

57 © 2017 Nokia
Parameters Introduced by Power Control (Contd.)
pMaxServingCell (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: pMaxServingCell
Description: Limits UE uplink transmission power in the serving cell and calculates the parameter for cell selection. The attribute is broadcast in SIB1. Value 1000 means the parameter is not included in
system information.
GUI Value Range: N/A
Actual Value Range: { -30..33, 1000 }
Recommended Value: 1000
Feature ID: N/A Feature Name: Idle Mode Support, Power Control
Guidance Notes : Changing this attribute can cause loss of traffic.

pZeroNominalPucch (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: pZeroNominalPucch
Description: The nominal component of the UE transmits power for Physical Uplink Control Channel (PUCCH).
GUI Value Range: N/A
Actual Value Range: { -127..-96 }
Recommended Value: -117
Feature ID: N/A Feature Name: Power Control , Scheduler
Guidance Notes: Changing this attribute can cause loss of traffic. If this parameter value is too large, the interference to neighboring cell increases and the overall network throughput decreases. If the
parameter value is too small the interference to neighbor cell decreases and the throughput of the local cell also decreases.

58 © 2017 Nokia
Parameters Introduced by Power Control (Contd.)
pZeroNominalPusch (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: pZeroNominalPusch
Description: The nominal component of the UE transmit power for Physical Uplink Shared Channel (PUSCH).
GUI Value Range: N/A
Actual Value Range: { -126…24 }
Recommended Value: -103
Feature ID: N/A Feature name: Power Control , Scheduler
Guidance Notes : Changing the value of pZeroNominalPusch might have an impact on the setting of puschPwrOffset64Qam. Changes may affect traffic

rachRootSequence (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: rachRootSequence
Description:
• The first root sequence number for Random Access Channel (RACH) preamble generation. RACH root sequence is broadcast as a part of system information distribution and used for preamble detection.
• If feature Automated Rach Root Sequence Allocation is not activated a parameter change triggers automatic cell lock/unlock.
• If feature Automated Rach Root Sequence Allocation is activated the parameter is changed without the need to lock/unlock the cell
GUI Value Range: N/A
Actual Value Range: { 0..837 }
Recommended Value: 386
Feature ID: FAJ 121 2026 Feature name: Automated RACH Root Sequence Allocation
Guidance Notes : Changing this attribute may affect the orthogonality of the preambles sequences for the cell and its neighboring cells.

59 © 2017 Nokia
Parameters Introduced by Power Control (Contd.)
crsGain (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: crsGain
Description: Sets the DL power of the Cell specific Reference Signal (CRS) relatively a reference level defined by the power of the PDSCH type A resource elements. If crsGain is +3dB, the CRS power is 3dB
higher than that of a PDSCH type A resource element. The settings crsGain=4.77db and 6dB are mapped to 3dB. These settings are not supported.
GUI Value Range: N/A
Actual Value Range: { -300, -200, -100, 0, 177, 300, 477, 600 }
Recommended Value: 0
Feature ID: N/A Feature Name: Power Control
Guidance Notes : The crsGain only takes effect if the configured number of antenna ports used in a sector is 2, 4, or 8. In the one port case, crsGain is hardcoded to 0dB. Takes effect on Cell lock/unlock.

pdschTypeBGain (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: pdschTypeBGain
Description: Sets the DL power of the PDSCH type B resource elements relatively the PDSCH type A resource elements. Values pdschTypeBGain=(0,1,2,3) define the gains (5/4,1,3/4,1/2) respectively
GUI Value Range: N/A
Actual Value Range: { 0, 1, 2, 3 }
Recommended Value: 0
Feature ID: N/A Feature Name: Power Control
Guidance Notes : The pdschTypeBGain=0 (gain=5/4) is not allowed if crsGain=1.77,3.0, 4.77,6.0 dB . This combination causes over allocation of DL mean radio power and attribute pdschTypeBGain is set to 1
(gain=1).
The pdschTypeBGain only takes effect if the configured number of antenna ports is 2,4, or 8. In the one port case, the power of resource elements for PDSCH type A and B is equal.

60 © 2017 Nokia
Parameters Introduced by Power Control (Contd.)
preambleInitialReceivedTargetPower (MO: ENodeBFunction >> EutranCellFDD ) Impact Area-Accessibility
Parameter Name: preambleInitialReceivedTargetPower
Description: Indicates the target UE transmit power for the PRACH expected by the eNodeB when PRACH preamble format is 0 is applied on the condition that requirements for preambles detection
performance are met.
GUI Value Range: NA
Actual Value Range: { -120..-90 }
Recommended Value: -110
Dependencies: N/A
Feature ID: N/A (Basic Feature); Feature Name: Random Access
Guidance Notes: A higher value of this parameter results in a higher success rate of random Access by initially sending the preambles but stronger interference on the neighboring cells. A smaller value
leads to opposite effect.

PowerRampStep (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: PowerRampStep
Description: This parameter is the power increase step of the random access preambles transmitted before the UE which receives the acquisition indicator in the random access process
GUI Value Range: N/A
Actual Value Range: { 1..8}
Recommended Value: 2
Feature ID: N/A (Basic Feature); Feature Name: Random Access
Guidance Notes: If this value is too high, the access process is shortened, but the probability of power waste is higher. If it is too low, the access process is lengthened, but the transmitting power is saved.

61 © 2017 Nokia
Layer: 3 Messages
System Information- SIB2

Figure 2.6: System Information

62 © 2017 Nokia
Internal Events: PmEvents List
Event Parameter Name Parameter Description Logical value Parameter Unit

Latest estimation of actual UE power headroom.

To convert parameter value to dB:
EVENT_PARAM_EST_POWER_HEADROOM - 0.1 dB
POWER_HEADROOM_DB = X * 0.1 - 23
[0, 1, 2, ..., 630] -> [-23, -22.9, -22.8 ..., 40]

The last reported PUSCH Power per PRB

To convert parameter value to dBm:
PUSCH received power = X*0.1 – 150.1
EVENT_PARAM_LAST_PUSCH_POWER_PER_PRB_REP
thus maps to [-150, -149.9, -149.8, …, 30.0] - 0.1dBm
ORTED
UE received power over the antennas used for combining in the serving cell, over the demodulation
reference signals
within the subframe, and over the granted PRBs expressed in dBm.

EVENT_PARAM_POWER_HEADROOM_PRB_USED The number of PRBs used, for the latest UL transmission with a Power Headroom Report - -

EVENT_PARAM_POWER_HEADROOM Index of UE Transmission Power Headroom, see 3GPP 36.133 - -

Number of samples for the power headroom with value < -19 dB. The measured sample is the latest
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_0 - -
value per second. See 3GPP TS 36.133.

Number of samples for the power headroom with -19 dB <= value < -15 dB. The measured sample is
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_1 - -
the latest value per second. See 3GPP TS 36.133.

63 © 2017 Nokia
Internal Events: PmEvents List (Contd.)
Event Parameter Name Parameter Description Logical value Parameter Unit

Number of samples for the power headroom with value -15 dB <= value < -11 dB. The measured sample
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_2 - -
is the latest value per second. See 3GPP TS 36.133.

Number of samples for the power headroom with -11 dB <= value < -7 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_3 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with -7 dB <= value < -3 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_4 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with -3 dB <= value < 1 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_5 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 1 dB <= value < 5 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_6 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 5 dB <= value < 9 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_7 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 9 dB <= value < 13 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_8 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 13 dB <= value < 17 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_9 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 17 dB <= value < 21 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_10 - -
latest value per second. See 3GPP TS 36.133.

64 © 2017 Nokia
Internal Events: PmEvents List (Contd.)
Event Parameter Name Parameter Description Logical value Parameter Unit

Number of samples for the power headroom with 21 dB <= value < 25 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_11 - -
latest value per second. See 3GPP TS 36.133.

Number of samples for the power headroom with 25 dB <= value < 29 dB. The measured sample is
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_12 - -
the latest value per second.
Number of samples for the power headroom with 29 dB <= value < 33 dB. The measured sample is
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_13 - -
the latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with 33 dB <= value < 37 dB. The measured sample is the
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_14 - -
latest value per second. See 3GPP TS 36.133.
Number of samples for the power headroom with value >= 37 dB. The measured sample is the latest
EVENT_PARAM_MDT_M2_UE_POWER_HEADROOM_15 - -
value per second. See 3GPP TS 36.133.
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_VALUE_POWE
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. -
R_CLASS_1
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_VALUE_POWE
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. -
R_CLASS_2
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.

65 © 2017 Nokia
Internal Events: PmEvents List (Contd.)
Event Parameter Name Parameter Description Logical value Parameter Unit
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_VALUE_POWE
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. -
R_CLASS_3
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_VALUE_POWE
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. -
R_CLASS_4
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_VALUE_POWE
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. -
R_CLASS_5
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.
Indicates the UE's power class (as defined in 3GPP TS 36.101 and 36.331) for the current cell's
EVENT_PARAM_UE_POWER_CLASS frequency band. Signaled in UE Capabilities as optional IE. - -
The parameter is set to UNAVAILABLE when the power class optional IE is not signaled by the UE.

66 © 2017 Nokia
 Contents
• Scheduling
• Overview
• Scheduling Detail
• Parameters and Counters
• Power Control
• Features Related to Power Control
• Power Control in Ericsson
• Parameters and Counters
• Link Adaptation

67 © 2017 Nokia
 Link Adaptation

68 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Link Adaptation
Uplink link adaptation
Uplink link adaptation, for example, a selection of modulation and channel coding, is controlled by the network. The eNB measures the uplink channel quality and orders the UE to use a specific modulation and
coding scheme (MCS) based on this. Other parameters may also be taken into account, such as UE power headroom, scheduled bandwidth, buffer content and acceptable delay.

Channel prediction:
• In the downlink, Gain to Interference and Noise Ratio (GINR) is used as a measure for channel prediction.
• It varies due to fading and interference. The slow fading component is tracked and used in link adaptation. GINR can be converted to Signal to Interference and Noise Ratio (SINR) by adding Power Spectral
Density (PSD) logarithmically.
• .
•SINRGain
= GINR + PSD
to Interference and Noise Ratio (GINR) is independent of tx power and used in order to ”translate” e.g. SINR RS to SINRPDSCH
• SINRRS= GINR + PSDRS
• SINRPDSCH = GINR + PSDPDSCH

• The UE estimates SINR based on the PSD of the downlink Reference Signals (RS) and PSD offset between Physical Downlink Shared Channel (PDSCH) and RS. This SINR is then converted to Channel Quality
Indicator (CQI) and reported to the RBS in CFRs.
• The CQI indicates the radio quality, and is used by the link adaptation function to select the transport format matching the channel conditions. This will lead to improved radio resource utilization

69 © 2017 Nokia
Link Adaptation (Contd.)
CFRs contain CQI, Precoding Matrix Indicator (PMI) and Rank Indicator (RI). The latter two are only used if a Multiple Input Multiple Output (MIMO) transmission with spatial multiplexing is present. PMI is only
used for closed loop spatial multiplexing, while CQI and RI are used also for open loop spatial multiplexing.
CFRs are transmitted either periodically over the Physical Uplink Control Channel (PUCCH) every 40ms or when the RBS triggers one over the Physical Uplink Shared Channel (PUSCH) based on downlink data
activity and the age of the earlier received CFR.
The RBS performs an adaptive adjustment of the SINR derived from CQI to compensate for errors and mismatches, and fulfills the targeted operating point.
CQI is estimated by the UE. It is up to the UE vendors to decide how to do it according to performance requirements

Figure 2.7: DL Channel Prediction

70 © 2017 Nokia
Link Adaptation (Contd.)
In the uplink, the channel quality estimate consists of predicted transmitted PSD, PSD TX, uplink Gain (path-loss) estimate, and "Noise+Interference" measurement. The PSD TX is estimated based on UE reported
PHR (power headroom report). This is used to estimate uplink gain together with measured PSD RX.
Link Adaptation uses link quality measurements to adapt the MCS. The MCSs consist of a modulation constellation (QPSK, 16QAM or 64QAM) and coding rate (ratio of information and coded bits). Link Adaptation
is used on new transmissions and HARQ retransmissions. It is not used in the uplink for random access message 3 ("RRC Connection Request").
For the uplink, Link Adaptation takes SINR into account. The SINR is based on measurements on the uplink demodulation reference signal. Worst case link adaptation is used until the first power headroom
report is received.
The following common channels use QPSK modulation: PBCH, PDCCH and PCFICH. PHICH uses BPSK

Figure 2.8: UL Channel Prediction

71 © 2017 Nokia
Link Adaptation (Contd.)
PDCCH Link Adaptation:
Multiple PDCCHs can be transmitted in one subframe, mapped to resource elements on one or several of the first three Orthogonal Frequency Division Multiplexing (OFDM) symbols not being used for
reference signals, PCFICH or PHICH.
PDCCH REs are divided into a number of Control Channel Elements (CCEs), each containing 36 REs.
The REs within a CCE are spread out in frequency and time to achieve diversity. One PDCCH can be mapped to 1, 2, 4 or 8 CCEs, which can belong to different OFDM symbols. Selection of number of CCEs is
done based on the same GINR estimate used for PDSCH link adaptation adjusted by an additional fixed margin
PDCCH is transmitted with QPSK modulation. Convolutional coding 1/3 and rate matching (to fit data onto CCEs) are applied to data on PDCCH

Figure 2.9: PDCCH Link Adaptation

72 © 2017 Nokia
Link Adaptation (Contd.)
PDSCH Link Adaptation:
• The quality requirement for this channel is HARQ OPP. The transport format parameters are MCS and TBS (Transport Block Size).
• The MCS is signaled to the UE in the scheduling assignment. The MCS together with the resource assignment will determine the TBS and coding rate.
• There are 29 possible MCS values for new transmissions
• The maximum TBS depends on the amount of data in the scheduler and capability of the UE.
• For HARQ retransmissions, three MCS values correspond to the modulation used. The TBS in this case is the same as the initial transmission and not signaled.
• The supported values of MOD for PDSCH can be QPSK, 16QAM and 64QAM. This corresponds to 2, 4 and 6 bits per modulation symbol respectively.
• The latter is only possible with a license. Link Adaptation is frequency selective in this release, which means that the selected MCS is based on the estimated channel quality over the assigned resource
blocks

73 © 2017 Nokia
Link Adaptation (Contd.)

MCS Index Modulation Order TBS Index MCS Index Modulation Order TBS Index
0 2 0 16 4 15
1 2 1 17 6 15
2 2 2 18 6 16
3 2 3 19 6 17
4 2 4 20 6 18
5 2 5 21 6 19
6 2 6 22 6 20
7 2 7 23 6 21
8 2 8 24 6 22
9 2 9 25 6 23
10 4 9 26 6 24
11 4 10 27 6 25
12 4 11 28 6 26
13 4 12 29 2
14 4 13 30 4 reserved
15 4 14 31 6

Figure 3.0: PDSCH Link Adaptation

74 © 2017 Nokia
Link Adaptation (Contd.)
PUSCH Link Adaptation:
• PUSCH link adaptation needs power headroom reporting to predict the PSDTX of UL transmissions.
• Power headroom reporting provides the serving RBS with information about the difference between the UE's maximum transmit power and the target power for PUSCH transmission.
• These reports are sent by the UE if the measured pathloss has changed by a given amount, or the time since the last report is a given amount.
• This is indicated by the parameters deltaPathloss and phrTimer parameters signaled by higher layers.
• Also, there is another parameter tPhrProhibited, which is the minimum time between a Power Headroom Report (PHR), even when the pathloss change is fulfilled. PHRs are only sent when there are
PUSCH allocations
.

Note: “deltaPathloss”, “phrTimer” and “tPhrProhibited” are not real parameter names! The parameters are non-configurable

75 © 2017 Nokia
Link Adaptation (Contd.)

Modulation Order Redundancy Version Modulation Order Redundancy

MCS Index IMCS TBS Index ITBS MCS Index IMCS TBS Index ITBS
Qm rvidx Qm Version rvidx
0 2 0 0 16 4 15 0
1 2 1 0 17 4 16 0
2 2 2 0 18 4 17 0
3 2 3 0 19 4 18 0
4 2 4 0 20 4 19 0
5 2 5 0 21 6 19 0
6 2 6 0 22 6 20 0
7 2 7 0 23 6 21 0
8 2 8 0 24 6 22 0
9 2 9 0 25 6 23 0
10 2 10 0 26 6 24 0
11 4 10 0 27 6 25 0
12 4 11 0 28 6 26 0
13 4 12 0 29 1
14 4 13 0 30 reserved 2
15 4 14 0 31 3

Figure 3.1: PUSCH Link Adaptation

76 © 2017 Nokia
Link Adaptation (Contd.)
PUSCH link adaptation differs to PDSCH link adaptation in the following ways:
• No scheduling grant needs to be transmitted for a retransmission if the allocation is sent in the
same frequency and transport format.
• The PSD is not constant between different allocations. This depends on the number of scheduled
blocks, where the upper bounds can be limited by UE power in order to avoid too low SINR.
• CFR and HARQ Acknowledgements can be multiplexed with uplink data over PUSCH

PUCCH Link Adaptation:

Link adaptation is not used for PUCCH

Figure 3.2: PUSCH Link Adaptation

77 © 2017 Nokia
Link Adaptation (Contd.)
PDCCH Power Boost:
The PDCCH power boost feature consists of two parts:
• An automatic boost of all CCE aggregation levels less than the maximum CCE aggregation level in the cell (usually 8 CCEs). This is mainly a capacity feature
• An optional boost of the maximum CCE aggregation level. The boost of the maximum CCE aggregation level is controlled by operator by a MOM parameter (pdcchPowerBoostMax). Up to 6 dB boost can be
set. The default boost of the maximum level is 0dB. This is mainly a coverage feature
The automatic boost gives an increased PDCCH capacity, while the boost of the maximum CCE aggregation level gives an increased coverage, e.g. for beam forming or Heterogeneous Network scenarios
Benefits:
• Increased cell coverage in beam forming (TM7/TM8) and Heterogeneous deployments.
• Boost of max CCE level 8 with pdcchPowerBoostMax > 0 dB
• Improved system capacity due to increased No of scheduled users per TTI (especially for VoLTE).
• Boost of all CCE aggregation levels 1, 2 and 4

The following tables show the max recommended settings for the pdcchPowerBoostMax

Figure 3.3: Recommended settings

78 © 2017 Nokia
Link Adaptation (Contd.)
Feature Operation:
PDCCH Control Channel Element (CCE) and Power are key resources of PDCCH transmission. Without this feature, only CCE resources are taken into account. PDCCH power is a fixed value, which enables
PDCCH power but CCE resources are wasted. The PDCCH Power Boost feature calculates the power boost value and CCE aggregation level, so PDCCH resources efficiency are increased, and the system
capacity is also improved. Furthermore, when the maximum aggregation level and maximum boost power are allocated, PDCCH cell coverage is improved.
Process Steps:
• CCE Aggregation Level and Boost Power Pre-calculation:
This function calculates the CCE aggregation level and the boost value based on CCE cost and PDCCH Signal to Interference and Noise Ratio (SINR) from the PDCCH link Adaptation feature. A User
Equipment (UE) at any cell position is supported to calculate the corresponding CCE aggregation level and boost power.
• Boost Value and PDCCH Power per OFDM Symbol Checking:
The requested maximum boost power level, given by the MOM parameter pdcchPowerBoostMax, is validated against the available PDCCH power in the control region.
• CCE Allocation:
CCE allocation is a basic function introduced as part of LTE basic, which is the baseline of the PDCCH Power Boost feature.

Supported Bandwidth:
The PDCCH Power Boost feature supports bandwidth of 3, 5, 10, 15, and 20 MHz.

79 © 2017 Nokia
Link Adaptation (Contd.)
Enhanced PDCCH Link Adaptation Feature:
• Enhanced PDCCH link adaptation feature allows efficient use of the PDCCH resource by having a better outer loop algorithm.
• The channel quality measurements reported to the RBS by each user are subject to measurements errors, reporting delays and channel fluctuations
• The Enhanced PDCCH Link Adaptation tries to correct these imperfections by adjusting the reported measurements in order to achieve the target block error rate (BLER) for PDCCH transmissions.
• This feature allows efficient use of the PDCCH resource while ensuring the quality of service requirements. This results in:
• Improved system capacity due to increased number of scheduled users per Transmission Time Interval (TTI), especially for Voice Over IP (VoIP) traffic.
• Better control and monitoring of the PDCCH error rate.
• Better VoLTE quality due to independent control of the PDCCH error rate for VoLTE UEs.

Feature Operation:
The basic PDCCH Link Adaptation uses the Physical Downlink Shared Channel (PDSCH) transmission success and a configurable offset to achieve the target Block Error rate (BLER) for PDCCH transmissions.
Enhanced PDCCH Link adaptation is based on PDCCH transmission success. It uses the PDSCH Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) feedback and the Physical Uplink Shared
Channel (PUSCH) detection results to determine whether or not a PDCCH transmission was successful.
In addition to achieving the target BLER, it makes efficient use of the PDCCH resources, which allows increased system capacity

80 © 2017 Nokia
Link Adaptation (Contd.)
This section describes the main process steps for the feature flow
• SINR Estimation:
• The Signal to Interference and Noise Ratio (SINR) estimation is based on the Channel Quality Indicator (CQI) report.
• PDCCH Outer Loop Adjustments:
• In order to satisfy the required BLER for PDCCH, the estimated SINR must be adjusted to compensate for the CQI estimation errors on the PDCCH.
• To determine the outer loop adjustment criteria, the Enhanced PDCCH Link Adaptation relies on the following elements:
• Success or failure of the PDCCH transmissions: The HARQ-ACK reports and the PUSCH detection results are used for this purpose. If the node detects a user HARQ response, either
negative or positive, the PDCCH transmission is considered successful. If no response is detected, the PDCCH transmission is considered failed. The node considers the transmission on the
PUSCH as failed if the Cyclic Redundancy Check (CRC) fails and no valid signal is received.
• Aggressive and conservative PDCCH allocation: The PDCCH allocation is considered conservative if the number of allocated Control Channel Elements (CCE) exceeds, within a predefined
range, the required number, and it is considered aggressive in the opposite case. The outer loop keeps track of adjustments made when allocation is aggressive or conservative, and it uses
this information to decide how to make the adjustment.
• In TDD, this feature is only applicable for UEs that are configured with HARQ-ACK bundling. Therefore, this feature is not applicable for UEs configured with Carrier Aggregation (CA).

Target BLER values are configured independently for CA, Voice over LTE (VoLTE), and non-CA and non-VoLTE services.

81 © 2017 Nokia
Parameters Introduced by Link Adaptation
pdcchTargetBler (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility
Parameter Name: pdcchTargetBler
Description: PDCCH target error rate for UEs that do not have any secondary cell configured and do not have any bearer mapped to a QCI with service Type of VoIP. In TDD, this parameter applies only to UEs
which are configured with HARQ-ACK bundling
GUI Value Range: N/A
Actual Value Range: { 1..200 }
Recommended Value: 24
Feature ID : FAJ1213051 Feature Name: Enhanced PDCCH Link Adaptation
Guidance Notes: A smaller value of this parameter results in a lower PDCCH BLER , and a larger value of this parameter results in a higher PDCCH BLER. If the PDCCH BLER is too high , both uplink and
downlink throughput decreases. If the PDCCH BLER is too low, the amount of PDCCH resources to be consumed increases, thereby decreasing the cell capacity and the number of UEs to be Scheduled.

pdcchOuterLoopUpStep (MO: ENodeBFunction >> EUtranCellFDD/TDD ) Impact Area-Accessibility

Parameter Name: pdcchOuterLoopUpStep
Description: PDCCH outer loop up step size for UEs that do not have any secondary cell configured and do not have any bearer mapped to a QCI with service Type of VoIP. In TDD, this parameter applies only
to UEs which are configured with HARQ-ACK bundling
GUI Value Range: N/A
Actual Value Range: { 0..100 }
Recommended Value: 8
Feature ID : FAJ1213051 Feature Name: Enhanced PDCCH Link Adaptation
Guidance Notes : N/A.

82 © 2017 Nokia
 Copyright and confidentiality
The contents of this document are proprietary and confidential property The contents of this document are provided "as is". Except as required
of Nokia. This document is provided subject to confidentiality obligations by applicable law, no warranties of any kind, either express or implied,
of the applicable agreement(s). including, but not limited to, the implied warranties of merchantability
and fitness for a particular purpose, are made in relation to the
This document is intended for use of Nokia’s customers and accuracy, reliability or contents of this document. NOKIA SHALL NOT BE
collaborators only for the purpose for which this document is submitted RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any
by Nokia. No part of this document may be reproduced or made available loss of data or income or any special, incidental, consequential, indirect
to the public or to any third party in any form or means without the or direct damages howsoever caused, that might arise from the use of
prior written permission of Nokia. This document is to be used by this document or any contents of this document.
properly trained professional personnel. Any use of the contents in this
document is limited strictly to the use(s) specifically created in the This document and the product(s) it describes
applicable agreement(s) under which the document is submitted. The are protected by copyright according to the
user of this document may voluntarily provide suggestions, comments applicable laws.
or other feedback to Nokia in respect of the contents of this document
("Feedback"). Nokia is a registered trademark of Nokia Corporation. Other product and
Such Feedback may be used in Nokia products and related specifications company names mentioned herein may be trademarks or trade names
or other documentation. Accordingly, if the user of this document gives of their respective owners.
Nokia Feedback on the contents of this document, Nokia may freely use,
disclose, reproduce, license, distribute and otherwise commercialize
the feedback in any Nokia product, technology, service, specification or
other documentation.

Nokia operates a policy of ongoing development. Nokia reserves the

right to make changes and improvements to any of the products and/or
services described in this document or withdraw this document at any
time without prior notice.

84 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
 Revision history and metadata

Document ID: Parameter Analysis Guideline-UE Power Control, DRX and Link Adaptation
Document Location:
Organization:

Version Description of charges Date Author Owner Status Reviewed by Reviewed date Approver Approval date

V1.1 Draft 28-08-2017 Hexamatics Nokia - Badri 30-08-2017

V1.2 Draft 04-09-2017 Hexamatics Nokia - Badri 05-09-2017

V1.3 Draft 08-09-2017 Hexamatics Nokia - Badri 11-09-2017

V1.4 Draft 16-09-2017 Hexamatics Nokia - Badri 20-09-2017

V1.5 Draft 24-09-2017 Hexamatics Nokia - Deepak 28-09-2017

V1.6 Final 30-09-2017 Hexamatics Nokia

85 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>