64-QAM Uplink

Contents
1 Introduction
1.1 Basic Characteristics
1.2 Benefits
1.3 Additional Information

2 Feature Operation
2.1 Network Requirements
2.2 <"Feature Operation Sequence Diagram" optional section>
2.3 <"Process Steps" optional section>

3 Parameters
3.1 Feature Configuration Parameters
3.2 Affected Parameters
3.3 <"Parameters Affecting the Feature" optional section>

4 Network Impact
4.1 <"Capacity" optional section>
4.2 <"Coverage" optional section>
4.3 <"Mobility" optional section>
4.4 <<other area> optional section>

5 Associated Features and Affected Functions

5.1 Prerequisite Features
5.2 Affected Features
5.3 Affected System Functions

6 Performance
6.1 KPIs
6.2 Counters
6.3 Events

7 O&M Information
7.1 Activate and Deactivate Feature

1 Introduction
This document describes the 64-QAM Uplink feature, which offers an increased uplink
throughput to UEs with 64-QAM capability in good covering areas, and makes the uplink
spectrum more efficient.
The benefits on uplink cell throughput increases if more receiving antennas are used. This
feature provides support of 64QAM modulation in the uplink for Category 5 UEs, and UL-
Category 5 and 13, defined in 3GPP TS 36.306 v12.4.0.

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature name: 64-QAM Uplink

Product DU-based node, see Feature Overview.

identity:

Baseband-based node, see Licensed Feature Overview.

Replaces: N/A

Dependencies

This feature has no prerequisite features.

This feature can affect the following RAN features:

 Uplink Multiuser MIMO

 Carrier Aggregation

1.2 Benefits
The 64-QAM Uplink feature enables higher order modulation on PUSCH, increases the
number of bits per symbol used in LTE physical layer resources, and improves throughput.

Benefits:

 Allows uplink peak rate 70 Mbps for 64QAM capable UEs in FDD 20 MHz
bandwidth
 Increase uplink throughput for 64QAM capable UEs in good coverage areas

1.3 Additional Information

More information about this feature and related topics can be found in the following 3GPP
documentation:

 36.211 v12.5.0 – 64QAM modulation mapping

 36.212 v12.4.0 – Multiplexing and channel coding
 36.213 v12.5.0 – Modulation order determination in PUSCH
 o MCS 0 – 28, are supported for Category 5 UEs, where MCS 21 – 28 are
used with 64QAM modulation
o Non-Category 5 UEs still support MCS 0 – 24 where MCS 21 – 24 are
used with 16QAM modulation
 36.331 v12.5.0 – Signaling of enable64QAM in PUSCH-ConfigCommon, as well
as UE capability signaling; Signaling of UE UL 64QAM capability and supported
bands
o enable64QAM is to true in SIB2 and Mobility Control Information, when
feature is enabled
 36.306 v12.4.0 – UE category definition; UE UL Category definition

2 Feature Operation
This section describes the 64-QAM Uplink feature in detail, including network configuration
requirements and operation flows.

2.1 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. See Section 7.1 for more details.

The following must <if applicable: "also"> be fulfilled at feature activation:>

<insert more criteria at feature activation>

2.2 <"Feature Operation Sequence Diagram" optional section>

2.3 <"Process Steps" optional section>

This section describes the main process steps for the feature flow.

2.3.1 <Process Step 1>

2.3.2 <Process Step 2>

3 Parameters
This section describes configuration parameters for the 64-QAM Uplink feature and
parameters affected by activating the feature.

3.1 Feature Configuration Parameters

Table 1 describes the feature parameters.
Table 1 Feature Parameters
Parameter Description
puschPwrOffset64Qam puschPwrOffset64Qam = 0 { 0..8 } Power offset to the target received
PUSCH Power Spectral Density (PSD) for 64-QAM-capable UEs. Used to
control the received SINR target. It is used to enable maximum
throughput for 64QAM, which in some configurations is not possible
otherwise, see dependencies. Dependency: Only relevant if the license
for 64-QAM Uplink is present and the feature is active. For 2Rx,
pZeroNominalPusch + puschPwrOffset64qam needs to be -100 dBm or
higher to achieve maximum throughput. Unit: 1 dB Disturbances:
Changes may affect traffic. Takes effect: Immediately.
Ul64QamEnabled Ul64QamEnabled = true Enables Ul64Qam on cell level. Only relevant if
the license for Ul64Qam is present and the feature is active. Takes
effect: Immediately

3.2 Affected Parameters

Table 2 describes the parameters affected by the feature.

Table 2 Affected Parameters

Parameter Description
<exampleParameterC> <Brief description>
<exampleParameterD> <Brief description>

3.3 <"Parameters Affecting the Feature" optional section>

Table 3 describes parameters that affect the feature.

Table 3 Parameters Affecting the Feature

Parameter Description
<exampleParameterC> <Brief description>
<exampleParameterD> <Brief description>

4 Network Impact
64QAM is selected based on estimated uplink channel quality. Since UE is power limited,
64QAM may be applied in good radio conditions with the knowledge of UE’s power
headroom. The overall uplink cell throughput and spectral efficiency is expected to increase,
however the amount of the increase depends on the ratio of 64QAM users and their channel
characteristics. Ideally it allows for single user uplink peak rate and spectral efficiency as
below:

 ~75 Mbps in 20 MHz FDD, while ~55 Mbps in case of 16QAM • 3.75 bits/s/Hz,
while 2.75 bits/s/Hz in case of 16QAM
 ~75 Mbps in 20 MHz FDD, while ~55 Mbps in case of 16QAM • 3.75 bits/s/Hz,
while 2.75 bits/s/Hz in case of 16QAM
 In practice there will be RBs allocated to PUSCH and PRACH. Thus a realistic
single user uplink peak rate is 70 Mbps with 90% 96 SBs allocation and 10% 90
SBs allocation.

4.1 <"Capacity" optional section>

This section provides information on the impact of the feature on network capacity.

4.2 <"Coverage" optional section>

This section provides information on the impact of the feature on network coverage.

4.3 <"Mobility" optional section>

This section provides information on the impact of the feature on mobility.

4.4 <<other area> optional section>

This section provides information about <...>.

5 Associated Features and Affected Functions

This section describes how the <feature name> feature affects other features and functions.

5.1 Prerequisite Features

Table 4 lists prerequisite features to the 64-QAM Uplink feature, that is, they must be active
prior to introducing the <feature name> feature.

Table 4 Prerequisite Features

Feature Description
<feature name 1> <optional description or comment if needed>

<feature name 2> <optional description or comment if needed>

5.2 Affected Features

Table 5 lists features that are affected by the 64-QAM Uplink feature.

Table 5 Affected Features

Feature Description
<feature name 1> <description of how this feature is affected>
<feature name 2> <description of how this feature is affected>

5.3 Affected System Functions

Table 6 lists functions affected by the 64-QAM Uplink feature.

Table 6 Affected System Functions

Function Description
<function name 1> <description of how this function is affected>
<function name 2> <description of how this function is affected>

6 Performance
This section describes performance indicators, counters, and events associated with the 64-
QAM Uplink feature.

6.1 KPIs
Table 7 lists the main Key Performance Indicators (KPIs) associated with the 64-QAM Uplink
feature.

Table 7 KPIs
KPI Description
CORE-B-PI:183 UL 64QAM Show the ratio of UL 64QAM feature usage.
Transport Ratio
CORE-B-PI:182 UL HARQ Extend existing PI “UL HARQ DTX Rate”
64QAM DTX Rate
CORE-B-PI:184 UL 64QAM Show the BLER for UL 64QAM
BLER
CORE-B-PI:83 UL HARQ Add 64QAM in the calculation.
Response rate
CORE-B-PI:143 UL HARQ Add 64QAM in the calculation.
Success Rate
CORE-B-PI:144 UL HARQ DTX Add 64QAM in the calculation.
Rate
CORE-B-PI:84 DL 64QAM Update PI name from “64QAM” to “DL 64QAM” since a similar UL one is
Transport Ratio created???
CORE-V-KPI:14 UDP UL Peak Link to new MARS requirements
Data Rate
CORE-B-KPI:49 UDP UL Link to new MARS requirement s
Average User Throughput

6.2 Counters
Table 8 lists the counters associated with the 64-QAM Uplink feature.

Table 8 Counters
Counter
pmMacHarqUlSucc64qam
pmMacHarqUlFail64qam
pmMacHarqUlDtx64qam
pmSinrPuschDistr
pmSinrPuschSectorCarrierDistr
pmUeCategoryDlUlCombDistr
Description
The total number of successful HARQ transmissions in the uplink
direction using a 64QAM modulation. Condition: To decide if it was
successful is based on the CRC check, not based on if RBS sends HARQ
ACK (RBS can use the ACK even if the transport block was not
successfully decoded in a way to control the HARQ). Counter type: ACC
Sampling rate: - Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
The total number of unsuccessful HARQ transmissions in the uplink
direction using a 64QAM modulation. Condition: To decide if it was
failed is based on the CRC check for received transport blocks (which
results in NACK). Counter type: ACC Sampling rate: - Scanner: Not
included in any predefined scanner Counter is reset after measurement
period: Yes
The total number of occasions when an uplink grant was meant for
HARQ transmission of a transport block using 64QAM modulation in the
uplink direction, where DTX is considered the reason for no reception of
HARQ in uplink in the eNB. Condition: To decide if it was DTX is based
on not receiving a granted uplink transmission using 64QAM
modulation. Counter type: ACC Sampling rate: - Scanner: Not included
in any predefined scanner Counter is reset after measurement period:
Yes
[0]: SINR <= -5 [1]: -5 < SINR <= -2 [2]: -2< SINR <= 2 [3]: 2 <
SINR <= 6 [4]: 6 < SINR <= 10 [5]: 10 < SINR <= 14 [6]: 14 < SINR
<= 17 [7]: 17 < SINR [7]: 17 < SINR <= 20 [8]: 20 < SINR
Distribution of the SINR values calculated for PUSCH. One bin added to
extend the range as done for pmSinrPuschDistr
Distribution of supported combinations for UE capability parameters ue-
CategoryUL and ue-CategoryDL for established UE contexts, according
to 3GPP TS 36.306 Table 4.1A-6. PDF ranges: [0]: ueCategoryDL = 0
and ueCategoryUL = 0 [1]: ueCategoryDL = 6 and ueCategoryUL = 5
[2]: ueCategoryDL = 7 and ueCategoryUL = 13 [3]: ueCategoryDL = 9
and ueCategoryUL = 5 [4]: ueCategoryDL = 10 and ueCategoryUL = 13
[5]: ueCategoryDL = 11 and ueCategoryUL = 5 [6]: ueCategoryDL =
12 and ueCategoryUL = 13 [7]: ueCategoryDL = 13 and ueCategoryUL
= 3 [8]: ueCategoryDL = 13 and ueCategoryUL = 5 [9]: ueCategoryDL
= 13 and ueCategoryUL = 7 [10]: ueCategoryDL = 13 and
ueCategoryUL = 13

More information about counters can be found in Managed Object Model (MOM).

6.3 Events
Table 9 lists the events associated with the 64-QAM Uplink feature.

Table 9 Events
Event Event Parameter Description
EVENT_PARAM_UE_HARQ_UL_SUCC_64QAM The total number of successful HARQ
transmissions in the uplink direction using a
64QAM modulation. Successful is based on
the CRC check, not based on if RBS sends
HARQ ACK (RBS can use the ACK even if the
transport block was not successfully decoded
in a way to control the HARQ)
EVENT_PARAM_UE_HARQ_UL_FAIL_64QAM The total number of unsuccessful HARQ
transmissions in the uplink direction using a
64QAM modulation.Failure is based on the
CRC check (which will result in an NACK).
 EVENT_PARAM_PER_UE_MAC_DTX_UL_64QAM The total number of occasions when an
uplink grant was meant for HARQ
transmission of a transport block using
64QAM modulation in the uplink direction,
where DTX is considered the reason for no
receiption of HARQ in uplink in the eNB.
EVENT_PARAM_SINR_MEAS_PUSCH_7 Number of samples for the measured SINR
on PUSCH, with 17 < SINR <= 20
EVENT_PARAM_SINR_MEAS_PUSCH_8 Number of samples for the measured SINR
on PUSCH, with 20 < SINR
EVENT_PARAM_UE_CAP_CATEGORY_DL_UL_COMB The ue-CategoryDL and ue-CategoryUL
Combination indicated by the UE, which sets
many other UE L2 parameters for the UE; it
has a range of [1..12]. See Table 4.1A-1,
4.1A-2, 4.1A-3, 4.1A-4, 4.1A-5 and 4.1A-6
3GPP Rel-12 TS 36.306.
EVENT_VALUE_UE_CATEGORY_DL_0_UL_0
EVENT_VALUE_UE_CATEGORY_DL_6_UL_5
EVENT_VALUE_UE_CATEGORY_DL_7_UL_13
EVENT_VALUE_UE_CATEGORY_DL_9_UL_5
EVENT_VALUE_UE_CATEGORY_DL_10_UL_13
EVENT_VALUE_UE_CATEGORY_DL_11_UL_5
EVENT_VALUE_UE_CATEGORY_DL_12_UL_13
EVENT_VALUE_UE_CATEGORY_DL_13_UL_3
EVENT_VALUE_UE_CATEGORY_DL_13_UL_5
EVENT_VALUE_UE_CATEGORY_DL_13_UL_7
EVENT_VALUE_UE_CATEGORY_DL_13_UL_13
EVENT_PARAM_SINR_MEAS_PUSCH_7_XL Number of samples for the measured SINR
on PUSCH, with 17 < SINR <= 20
EVENT_PARAM_SINR_MEAS_PUSCH_8_XL Number of samples for the measured SINR
on PUSCH, with 20 < SINR
EVENT_PARAM_UE_HARQ_UL_SUCC_64QAM_XL The total number of successful HARQ
transmissions in the uplink direction using a
64QAM modulation. Successful is based on
the CRC check, not based on if RBS sends
HARQ ACK (RBS can use the ACK even if the
transport block was not successfully decoded
in a way to control the HARQ)
EVENT_PARAM_UE_HARQ_UL_FAIL_64QAM_XL The total number of unsuccessful HARQ
transmissions in the uplink direction using a
64QAM modulation. Failure is based on the
CRC check (which will result in an NACK).
EVENT_PARAM_PER_UE_MAC_DTX_UL_64QAM_XL The total number of occasions when an
uplink grant was meant for HARQ
transmission of a transport block using
64QAM modulation in the uplink direction,
where DTX is considered the reason for no
reception of HARQ in uplink in the eNB

More information about events can be found in PM Event List (DU-based node) or Lists
(Baseband-based node).

7 O&M Information
This section provides Operation and Maintenance (O&M) information for the 64-QAM Uplink
feature.
7.1 Activate and Deactivate Feature
Activating the feature requires that the corresponding license is installed. When the license
is installed, an MO instance Ul64Qam is automatically created.

Table 10 Feature MO Instance

Node type MO instance
DU-based node MO instance is OptionalFeatureLicense= Ul64Qam
Baseband-based node MO instance is FeatureState= Ul64Qam

Feature activation and deactivation are described in Manage Licenses.