You are on page 1of 10

LTE1130: Dynamic PUCCH Allocation Page 1 of 10

LTE Radio Access, Rel. TD-LTE 16A, Operating Documentation, Issue 02 (HTML) [2016-08-27 06:25 GMT+2] >
Features > TD-LTE16A, Feature Descriptions and Instructions > Descriptions of radio resource management and
telecom features

LTE1130: Dynamic PUCCH Allocation

Benefits, functionality, system impact, reference data, instructions of the feature


The LTE1130: Dynamic PUCCH Allocation feature introduces support for a dynamic allocation of the
physical uplink control channel (PUCCH) resources. This is done by adjusting the channel state
indicator (CSI) and uplink scheduling request (SR) periodicity for the UEs, based on system load.

LTE1130 benefits
The LTE1130: Dynamic PUCCH Allocation feature provides the following benefits:
• The operator can configure the physical uplink control channel (PUCCH) with simplified O&M
settings.
• In cells that supports high loads, the feature enables economizing the PUCCH resource
allocation, thus limiting the required PUCCH overhead.
• In low load conditions all UEs have a short CSI or SRI periodicity. Thanks to that performance
is improved. When the load increases, all UEs get a slower pace periodicity, and the eNB
tries to allocate CSI or SR in an optimal way.

LTE1130 functional description


Functional overview
The physical uplink control channel (PUCCH) is used to transmit the uplink control information (UCI),
which includes:
• scheduling requests (SR)
• HARQ ACK/NACK in response to DL transmissions in physical downlink shared channel
(PDSCH)
• channel state information (CSI), which includes:
◦ channel quality indicators (CQI)
◦ MIMO-related feedback such as the rank indicators (RI) or the precoding matrix
indicators (PMI)
The LTE1130: Dynamic PUCCH Allocation feature simplifies process of PUCCH configuration. The
feature introduces:
• dynamic switching between channel state indicator (CSI) periodicity: 40 ms and 80 ms
• dynamic switching between UL scheduling request (SR) periodicity: 10 ms, 20 ms, and 40 ms
Switching between different periodicities of SR/CSI depends on a cell load, which is related to number
of RRC Connected UEs in the cell.
The adaptation of the CSI or SR periodicity is done only for UEs for which reconfiguration needs to be
applied. To avoid generating extra signaling, new CSI or SR periodicity is given to every UE
experiencing one of the following events:
• RRC Idle to RRC Connected state transition
• UE entering the cell via handover

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 2 of 10

• secondary cell (SCell) configuration or reconfiguration


The functionality can be enabled or disabled per cell with the O&M setting, which requires cell locking.

PUCCH size determination


The eNB automatically calculates the required PUCCH resources based on selected values of PUCCH
parameters (listed below),system bandwidth and the following feature configuration:
• Carrier-aggregation-related features, which are activated with the actDLCAggr parameter.
Additionally, the maxNumScells parameter needs to be configured; value 1 supports 2CC-
capable UEs, and value 2 supports 2CC- and 3CC-capable UEs.
• MIMO-related features. The dlMimoMode parameter configuration is mandatory. The
number of required CSI resources to each UE when the rank indication (RI) reporting is
required depends on this parameter value.
• Enhanced inter-cell interference coordination (eICIC) features. The actEicic parameter
activates eICIC-related features.
• Discontinuous-reception (DRX)-related features, which are activated with the actDrx or
actSmartDrx parameter.
The PUCCH size is fixed and adjusted to calculated maximum number of RRC connected UEs
(maxNumRrc). When maximum number of RRC connected UEs value is known, the system
automatically chooses number of PRBs needed for CSI and SR. The maximum number of RRC
connected UEs is calculated according to the formula:
maxNumRrc = maxNumActUE + aPucchMinNumRrcNoDrb + max (aPucchAddAUeRrHo,
aPucchAddAUeTcHo).
If emergency handling is active (when actEmerCallRedir or actIMSEmerSessR9LNBTS
parameter is enabled) number of RRC connected UEs is extended:
maxNumRrc = maxNumActUE + aPucchMinNumRrcNoDrb + max (aPucchAddAUeRrHo,
aPucchAddAUeTcHo) + aPucchMinNumEmergencySessions
Parameters which are taken into account:
• actAutoPucchAlloc – This is an activation flag for the LTE1130 feature.
• maxNumActUE – This is a threshold for the maximum number of active UEs in the cell. Active
UEs are UEs with at least one data radio bearer (DRB). This parameter needs to be
configured based on the differences in bandwidth and a BTS type. It is online configurable
and below the expected system behavior when the parameter is modified is listed:
◦ If the maxNumActUE parameter is set to a smaller value than the actual state, it is
immediately implemented, but the PUCCH reconfiguration is not performed.
◦ If the maxNumActUE parameter is set to a higher value than the actual state (but
still within the capacity of the actual PUCCH configuration), it is immediately
implemented because there is no need of PUCCH reconfiguration.
◦ If the maxNumActUE parameter is set to a higher value than the actual state (but
above the actual PUCCH configuration), then it is rejected, the PUCCH
reconfiguration is not needed.
• aPucchMinNumEmergencySessions – This parameter determines the resources
reserved for emergency calls. The maximum margin depends on the bandwidth of a cell.
• aPucchAddAUeTcHo – This is an additional margin for the maximum number of active UEs
in the cell, accessing the cell via handover with HO-cause: "Time Critical HO". This margin is
added to the maxNumActUE threshold. The maximum margin depends on the bandwidth of a
cell.
• aPucchAddAUeRrHo – This is an additional margin for the maximum number of active UEs
in the cell, accessing the cell via handover with HO-cause: "HO desirable for radio reasons".
This margin is added to the maxNumActUE threshold. The maximum margin depends on the
bandwidth of a cell.

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 3 of 10

• aPucchMinNumRrc – This parameter specifies the minimum number of RRC-connected


UEs to be supported per cell; if the operator wants to have a dynamic PUCCH configuration
with at least four PRBs, instead of only two, this can be managed with this parameter.
• aPucchMinNumRrcNoDrb – This parameter configures a reserve for UEs that shall be able
to do bearerless actions such as tracking area updates when the maxNumActUE threshold is
configured near to the HW limit of a cell (which also depends on bandwidth). Additionally this
is margin for UE entering the cell with the RRC connection request cause: MO signaling.
• aPucchSrPeriodUpperLimit – This parameter defines the upper limit of the scheduling
request periodicity to be used in the cell by the PUCCH algorithm.
• selectPrachRegion – This parameter defines the selected PRACH region automatically
assigned by the PUCCH algorithm when the LTE1130: Dynamic PUCCH Allocation feature is
activated.
• aPucchId – This parameter is the naming atrribute of APUCCH managed object class and
does not require manual configuration.
• mPucchId – This parameter is the naming atrribute of MPUCCH managed object class and
does not require manual configuration.
The system derives PUCCH configuration parameters automatically and fills the following read-only
attributes in the APUCCH managed object class in BTS Site Manager:
• assignedN1PucchAn
• assignedDeltaPucchShift
• assignedPhichDur
• assignedPhichRes
• assignedPrachFreqOff
• assignedNPucchF3Prbs
• assignedNCqiRb
With the LTE1130 feature, the following parameters which were used for manual configuration of
PUCCH are now located under the MPUCCH managed object class in BTS Site Manager:
• n1PucchAn
• deltaPuchShift
• nCqiRb
• nPucchF3Prbs
• riEnable
• riPerM
• riPerOffset
• cqiPerNp
• cellSrPeriod

Performance monitoring
The purpose of the counters introduced with the LTE1130 feature is to indicate how many PUCCH
resources are used within the same transmission time interval (TTI).

Meaning of the reported faults


During feature configuration the following faults can be reported:
• 6294 – Not enough PUSCH resources for PRACH
This fault is reported when the operator configures parameters in such a way that the PRACH
channel is not configurable.
• 6295 – PUCCH configuration inconsistency
This fault is reported when the number of UEs requested by the operator is not achievable
(this is because the maximum PUCCH size defined by the automatic PUCCH configuration
has been reached). In this case the configuration with the highest available number of UEs is

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 4 of 10

selected instead. The BTS informs the operator through the fault report that the requested
number of UEs is not achievable, and then operates normally.

LTE1130 system impact


LTE1130: Dynamic PUCCH allocation impact on features and system performance and capacity

Interdependencies between features


The LTE1130: Dynamic PUCCH Allocation feature is impacted by the following features:
• Carrier-aggregation-related features
• MIMO-related features
• Enhanced-inter-cell-interference-coordination (eICIC)-related features
• Discontinuous-reception (DRX)-related features
All these features are taken into account for the correct calculation of the PRB resources required for
PUCCH allocation.

Impact on interfaces
The LTE1130: Dynamic PUCCH Allocation feature has no impact on interfaces.

Impact on network management tools


The LTE1130: Dynamic PUCCH Allocation feature has no impact on network management tools.

Impact on system performance and capacity


The LTE1130: Dynamic PUCCH Allocation feature impacts system performance as follows:
• The dynamic PUCCH allocation feature adjusts the CQI and SR periodicity, for UEs changing
the RRC configuration, based on the PUCCH load. In low-loaded cells, the throughput might
be slightly increased due to more frequent CQI reports. However, the resulting PUCCH
efficiency does not significantly impact throughput performance. Therefore, the feature does
not warrant performance requirements for throughput.
The LTE1130: Dynamic PUCCH Allocation feature has no impact on system capacity.

LTE1130 reference data


LTE1130: Dynamic PUCCH Allocation requirements, faults and reported alarms, measurements and
counters, parameters, and sales information

Requirements

Table: LTE1130: Dynamic PUCCH Allocation hardware and software requirements

Flexi Multiradio 10 Flexi Multiradio 10 Flexi Zone Micro Flexi Zone Access
System release AirScale BTS
BTS Indoor BTS BTS Point

TD-LTE 16A TL16A TL16A TL16A TL16A TL16A

Flexi Zone Controller OMS UE NetAct MME SAE GW

TL16A LTE OMS16A 3GPP R8 mandatory NetAct 16.8 support not required support not required

BTS faults and reported alarms

Table: New BTS faults introduced by LTE1130

Reported alarms
Fault ID Fault name
Alarm ID Alarm name

6294 Not enough PUSCH resources for PRACH 7653 CELL FAULTY

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 5 of 10

Reported alarms
Fault ID Fault name
Alarm ID Alarm name

6295 PUCCH configuration inconsistency 7655 CELL NOTIFICATION

For fault descriptions, see TD-LTE BTS Alarms and Faults.

Commands
There are no commands related to the LTE1130: Dynamic PUCCH Allocation feature.

Measurements and counters

Table: New counters introduced by LTE1130

Counter ID Counter name Measurement

M8011C189 Allocation of 40 ms CQI reporting periodicity on PUCCH LTE Cell Resource

M8011C190 Allocation of 80 ms CQI reporting periodicity on PUCCH LTE Cell Resource

M8011C191 Allocation of 10 ms SR reporting periodicity on PUCCH LTE Cell Resource

M8011C192 Allocation of 20 ms SR reporting periodicity on PUCCH LTE Cell Resource

M8011C193 Allocation of 40 ms SR reporting periodicity on PUCCH LTE Cell Resource

For counter descriptions, see LTE Performance Measurements and Key Performance Indicators.

Key performance indicators


There are no key performance indicators related to the LTE1130: Dynamic PUCCH Allocation feature.

Parameters

Table: New parameters introduced by LTE1130

Managed Parent
Full name Abbreviated name
object structure

Activation of automatic actAutoPucchAlloc LNCEL -


PUCCH allocation

Automatic PUCCH aPucchAddAUeRrHo APUCCH -


allocation, add number UEs
RR HO

Automatic PUCCH aPucchAddAUeTcHo APUCCH -


allocation, add number UEs
TC HO

Automatic PUCCH aPucchMinNumEmergencySessions APUCCH -


allocation, min num.
emergency sessions

Automatic PUCCH aPucchMinNumRrc APUCCH -


allocation, min number RRC

Automatic PUCCH aPucchMinNumRrcNoDrb APUCCH -


allocation, min number RRC
TAU

Automatic PUCCH aPucchSrPeriodUpperLimit APUCCH -


allocation, upper SR
periodicity

assignedDeltaPucchShift APUCCH -

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 6 of 10

Managed Parent
Full name Abbreviated name
object structure

Delta cyclic shift used in


PUCCH allocation

ACK/NACK offset used in assignedN1PucchAn APUCCH -


PUCCH allocation

PUCCH bandwidth for CQI assignedNCqiRb APUCCH -


used in PUCCH allocation

PRBs for HARQ Format 3 assignedNPucchF3Prbs APUCCH -


used in PUCCH allocation

PHICH duration used in assignedPhichDur APUCCH -


PUCCH allocation

PHICH resource used in assignedPhichRes APUCCH -


PUCCH allocation

PRACH frequency offset assignedPrachFreqOff APUCCH -


used in PUCCH allocation

Selection of PRACH region selectPrachRegion APUCCH -


in automatic PUCCH
allocation

Automatic PUCCH aPucchId APUCCH -


configuration identifier

Manual PUCCH configuration mPucchId MPUCCH -


identifier

Table: Parameters modified by LTE1130

Managed Parent
Full name Abbreviated name
object structure

Add number active UEs radio reason addAUeRrHo MPUCCH -


handover

Add number active UEs time addAUeTcHo MPUCCH -


critical handover

Add Emergency Sessions addEmergencySessions MPUCCH -

Cell Sr Periodicity cellSrPeriod MPUCCH -

CQI periodicity network period cqiPerNp MPUCCH -

Delta cyclic shift for PUCCH deltaPucchShift MPUCCH -

Max Number RRC maxNumRrc MPUCCH -

Max Number RRC Emergency maxNumRrcEmergency MPUCCH -

ACK/NACK offset n1PucchAn MPUCCH -

PUCCH bandwidth for CQI nCqiRb MPUCCH -

Number of PUCCH PRBs for HARQ nPucchF3Prbs MPUCCH -


Format 3

PHICH duration phichDur MPUCCH -

PHICH resource phichRes MPUCCH -

Rank indication reporting enable riEnable MPUCCH -

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 7 of 10

Managed Parent
Full name Abbreviated name
object structure

Multiplier M for periodic RI riPerM MPUCCH -


reporting period

Periodic RI reporting offset riPerOffset MPUCCH -

Table: Existing parameters related to LTE1130

Managed Parent
Full name Abbreviated name
object structure

Activation of downlink carrier actDLCAggr LNBTS -


aggregation

Activate emergency call via actEmerCallRedir LNBTS -


redirection

Activate support of IMS emergency actIMSEmerSessR9 LNBTS -


sessions for Rel 9 UE

Activate multiple bearers actMultBearers LNBTS -

Activate DRX actDrx LNCEL -

Activate fast adaptive MIMO switch actFastMimoSwitch LNCEL -

Activate load adaptive PDCCH actLdPdcch LNCEL -

Add number DRB radioReasHo addNumDrbRadioReasHo LNCEL -

Add number DRB timeCriticalHo addNumDrbTimeCriticalHo LNCEL -

Add number QCI1 DRB for addNumQci1DrbRadioReasHo LNCEL -


radioReasHo

Add number QCI1 DRB for addNumQci1DrbTimeCriticalHo LNCEL -


timeCriticalHo

Downlink MIMO mode dlMimoMode LNCEL -

Maximum number of OFDM symbols for maxNrSymPdcch LNCEL -


PDCCH

Max number act DRB maxNumActDrb LNCEL -

Maximum number of active UEs maxNumActUE LNCEL -

Max number of secondary cells for maxNumScells LNCEL -


DL carrier aggr

PRACH frequency offset prachFreqOff LNCEL -

PUCCH cyclic shift for mixed pucchNAnCs LNCEL -


formats

DRX smart profile 2 drxSmartProfile2 SDRX -

DRX smart profile 3 drxSmartProfile3 SDRX -

DRX smart profile 4 drxSmartProfile4 SDRX -

DRX smart profile 5 drxSmartProfile5 SDRX -

For parameter descriptions, see TD-LTE BTS Parameters.

Sales information

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 8 of 10

Table: LTE1130 sales information

Product structure class License control Activated by default

Application software (ASW) Pool license No

Activating and configuring LTE1130


Instructions to activate and configure the LTE1130: Dynamic PUCCH Allocation feature using the BTS
Site Manager.
Before you start
• Procedure notifications
◦ If feature activation requires only eNB reconfiguration, a cell lock is performed as a
result. In case full commissioning is performed, the eNB will restart.

• Feature interdependencies

◦ The LTE1130: Dynamic PUCCH Allocation feature is impacted by the following
features:
◾ Carrier-aggregation-related features
◾ MIMO-related features
◾ Enhanced-inter-cell-interference-coordination (eICIC)-related features
◾ Discontinuous-reception (DRX)-related features

All these features are taken into account for the correct calculation of the PRB
resources required for PUCCH allocation.

• Preconfiguration
◦ The Activation of automatic PUCCH allocation
(actAutoPucchAlloc) parameter is set to false.
◦ There is no APUCCH instance configured under any of the LNCEL-managed object.

Procedure

1 Start the BTS Site Manager application and establish the connection to the BTS.

2 Start commissioning.

Sub-steps

a) Select View ► Commissioning or click Commissioning on the View Bar on the left.
The BTS Site checkbox, located in the Target section, is selected by default. This is the recommended setting.

b) Use the Template, Manual, or Reconfiguration option, depending on the actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNCEL object.

Object path: MRBTS ► LNBTS ► LNCEL

5 Set the Activation of automatic PUCCH allocation (actAutoPucchAlloc) value to true.

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 9 of 10

6 Create an APUCCH-managed object under the LNCEL instance.

Configure all parameters located in the APUCCH-managed object.

Note: Optionally, the MPUCCH-managed object can be deleted from the LNCEL instance after creating and configuring APUCCH
managed object, but it is recommended to keep it.

7 In case more LNCEL instances exist, execute step 5 and step 6 on every LNCEL object.

8 Send the commissioning plan file to the BTS.

Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

• If the BTS has not been commissioned, select All parameters.

• If the BTS has been already commissioned, select Only changes.

c) Click Send Parameters.

Result
If feature activation requires only eNB reconfiguration, a cell lock is performed as a result. In case full
commissioning is performed, the eNB will restart.
After successful feature activation, the eNB connects to the management system and starts the
required alignment.

Deactivating LTE1130
Instructions to deactivate the LTE1130: Dynamic PUCCH Allocation feature using the BTS Site
Manager.
Before you start
• Procedure notifications
◦ If feature deactivation requires only eNB reconfiguration, a cell lock is performed as
a result. In case full commissioning is performed, the eNB will restart.

• Preconfiguration
The LTE1130 feature is activated.

Procedure

1 Start the BTS Site Manager application and establish the connection to the BTS.

2 Start commissioning.

Sub-steps

a) Select View ► Commissioning or click Commissioning on the View Bar on the left.
The BTS Site checkbox, located in the Target section, is selected by default. This is the recommended setting.

b) Use the Template, Manual, or Reconfiguration option, depending on the actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018
LTE1130: Dynamic PUCCH Allocation Page 10 of 10

4 Go to the LNCEL object.

Object path: MRBTS ► LNBTS ► LNCEL

5 Set the Activation of automatic PUCCH allocation (actAutoPucchAlloc) value to false.

6 If an MPUCCH-managed object under the LNCEL instance has been removed during feature activation, add and configure this
object.

It is not required to remove the APUCCH-managed object. After deactivating the LTE1130 feature, a manual PUCCH allocation is performed
based on the configuration in the MPUCCH-managed object.

7 Send the commissioning plan file to the BTS.

Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

• If the BTS has not been commissioned, select All parameters.

• If the BTS has been already commissioned, select Only changes.

c) Click Send Parameters.

Result
If feature deactivation requires only eNB reconfiguration, a cell lock is performed as a result. In case full
commissioning is performed, the eNB will restart.
After feature deactivation, both APUCCH- and MPUCCH-managed objects can exist in parallel. The
algorithm will obtain the values from the correct class instance.

© 2016 Nokia. All rights reserved.

http://localhost:1500/informationbrowser/topic/m155578004_html/htm/docs/td16a/c13... 2/13/2018