PUCCH Management (NR22.2) 1112864

PUCCH Management
Product Version: NR22.2
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P. R. China
Postcode:518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright ©2020 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties.
Any reproduction or distribution of this document or any portion of this document, in any
form by any means, without the prior written consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by contractual conﬁdentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or
service marks, of ZTE CORPORATION or of their respective owners.
This document is provided“as is”, and all express, implied, or statutory warranties,
representations or conditions are disclaimed, including without limitation any implied
warranty of merchantability, ﬁtness for a particular purpose, title or non-infringement. ZTE
CORPORATION and its licensors shall not be liable for damages resulting from the use of or
reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights
or applications covering the subject matter of this document. Except as expressly provided
in any written license between ZTE CORPORATION and its licensee, the user of this
document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product
without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Serial Number:2023-03-05
PUCCH Management
PUCCH Management
1 About This Document
1.1 Personal Data Security Statement
Some of the features listed in this document need users’ personal data during provisioning, including the SUPI, IMSI, IMEI, MSISDN, and UEIP.
These features are used for the purpose of implementing the service procedures or location procedures specified by 3GPP, optimizing service
experience of users, and facilitating system maintenance. When activating these features, you shall comply with local laws and regulations on
personal data protection and privacy protection.For any inquiries on the legality of activating these features, please consult your legal
department.
1.2 Changes
This section describes the changes between different versions of the product, including two types of changes:
Technical changes: technical changes and parameter changes between different versions.
Description changes: description and structure changes between different versions, including content optimization and supplementation.
Change Type Change Date Description Parameter Change
Technical changes 2023-01-30 Compared with the NR22.1 version, there is no technical changes. None
Description changes 2023-01-30 Compared with the NR22.1 version, there is no description change. None
2 Document Description
2.1 Covered Features
The following table lists the features covered in this document.
Table 1 Covered Feature List
No. NR22.2 Featur NR22.2 Feature N NR21.2 Feature ID and Feature Name Scenario Refer to
e ID ame
1 ZNR-RB-0050 Channel ZNR03-08-010 Basic Physical Layer Support SA&NSA [](4 PUCCH)
Management ZNR03-08-080 Long PUCCH 6 PUCCH Capacity Adaptation M
ZNR03-08-085 Short PUCCH anagement
ZNR11-00-020 PUCCH Blanking
ZNR03-08-080 PUCCH Capacity Adaptation
Management
2.2 Correlation with Other Features
Table 2 Correlation with Other Features
Feature ID Feature Name Required Feature Mutually Exclusive Feature Impacted Feature
ZNR-RB-0050 Channel Management None None None
2.3 Terms and Definitions
For the related terms and definitions, refer to the following table.
Table 3 Terms and Definitions
Term Full Name Definition
ACK ACKnowledgment Indicates that downlink or uplink data is received correctly.
3 - 108
PUCCH Management
BWP Bandwidth Part A cell may have UEs that vary in capability levels or services types, and the supported bandwidths vary with
terminals. Therefore, the BWP concept is introduced, and BWPs are divided into UL/DL common BWPs and
UL/DL-dedicated BWPs.
CORESET Control-Resource A control-resource set consists of some resource blocks in the frequency domain and some symbols in the
Set time domain.
CP-OFDM Cyclic prefix Orthogonal Frequency Division Multiplexing (OFDM) based on the cyclic prefix.
Orthogonal
Frequency-
Division Multiple
CQI Channel Quality Channel quality indicator is the channel measurement in accordance with CSI-RS reported from UE. The
Indicator gNodeB can use CQI to compute DL schedule MCS.
CSI Channel State Including the CQI/PMI/RI/IM information. Used to notify the gNodeB of the downlink channel quality to help
Information the gNodeB with downlink scheduling.
CSI-IM Channel State A resource set consists of some resource elements ,and can be used for interference measurement.
Information-
Interference
Measurement
CSI-RS Channel State CSI-RS is a physical signal used for CSI measurement. the CSI-RS can be used for RSRP measurement, CQI
Information measurement, PMI measurement, and Tracking function.
Reference Signal
DCI Downlink Control The downlink control message contains the RB resource allocation information, modulation scheme MCS,
Information and HARQ process ID. In the NR protocol, DCI0_x indicates the allocation of PUSCH resources, and DCI1_x
indicates the allocation of PDSCH resources. In addition, other DCI formats are used to control other
information.
DMRS Dedicated The DMRS is the basic physical signal in 5G NR system, and used for physical channel estimation and channel
Demodulation measurement.
Reference Signal
Front Front loaded Front-loaded DMRS refers to the DMRS that is in front of a PRB so that the UE can use the DMRS for
loaded DMRS demodulation quickly.
DMRS
HARQ Hybrid Automatic Data requested to be resent automatically in hybrid mode.

Repeat reQuest
LDPC Low Density A linear error correcting code used for data coding and decoding in 5G NR.
Parity Check Code
MU- Multi-User A technology that uses the gain of multi-antenna spatial diversity and selects multiple unrelated UEs to
MIMO Multiple-Input transfer data at the same time on the same time-frequency resource.
Multiple-Output
NACK Negative Indicates that downlink or uplink data is received incorrectly.

ACKnowledgment
PBCH Physical Physical-layer broadcast channel, which carries the BCH.

Broadcast
Channel
PDCCH Physical Downlink Physical-layer downlink control channel, which carries the Downlink Control Information (DCI).
Control Channel
PDSCH Physical Downlink Physical-layer downlink shared channel, which carries the downlink data.
shared Channel
PMI Precoding Matrix Precoding Matrix Indicator is the channel measurement in accordance with CSI-RS reported from UE. The
Indication gNodeB can use PMI to get Precoding Matrix for this UE.
PRACH Physical Random Physical-layer random access channel, which carries the RACH.
Access Channel
PSS Primary A physical used for slot synchronization and the detection of physical-layer identity
Synchronization
Signal
4 - 108
PUCCH Management
PUCCH Physical Uplink Physical-layer uplink control channel, which carries the Uplink Control Information (UCI).
Control Channel
PUSCH Physical Uplink Physical-layer uplink shared channel, which carries the Uplink Data Information and UCI.
Shared Channel
RI Rank Indicator The flow number of PDSCH that can be transmitted.
SC-OFDM Single Carrier The SC-OFDM waveform is a waveform which is processed by the DFT before modulation. It has single carrier
Orthogonal feature and has a peak-to-average ratio lower than OFDM waveform.
Frequency-
Division
Multiplexing
TA Timing Advance Result of time offset measurement
2.4 Feature Difference Descriptions
2.4.1 Difference Between FR1 FDD and FR1 TDD
Table 4 Difference Between FR1 FDD and FR1 TDD
Feature Difference Description Refer to
Basic Physical Layer Support Both FR1 FDD and FR1 TDD are supported, there is no difference. 3 Overview
Long PUCCH Both FR1 FDD and FR1 TDD are supported, 4.1 Principle
but PUCCH resource parameters configured on the UME are different.
Short PUCCH Neither FR1 FDD nor FR1 TDD are supported. 4.1 Principle
PUCCH blanking Both FR1 FDD and FR1 TDD are supported, there is no difference. 4.1 Principle
PUCCH Capacity Adaptation Management Both FR1 FDD and FR1 TDD are supported, there is no difference. 6.1 Principle
2.4.2 Difference Between NSA and SA Networks
Table 5 Difference Between NSA and SA Networks
Basic Physical Layer Support Both NSA and SA are supported, there is no difference. 3 Overview
Long PUCCH Both NSA and SA are supported, there is no difference. 4.1 Principle
Short PUCCH Both NSA and SA are supported, there is no difference. 4.1 Principle
PUCCH blanking Both NSA and SA are supported, there is no difference. 4.1 Principle
PUCCH Capacity Adaptation Management Both NSA and SA are supported, there is no difference. 6.1 Principle
2.4.3 Difference Between FR1 and FR2
Here in this document, FR1 refers to 410MHz~7125MHz, FR2 refers to 24250MHz~52600MHz. For detailed definition of FR1 and FR2, refer to 5.1
General in 3GPP TS 38.104 V15.5.0.
Table 6 Difference Between FR1 and FR2
Basic Physical Layer Support Both FR1 and FR2 are supported, there is no difference. 3 Overview
Long PUCCH Support FR1 only. 4.1 Principle
Short PUCCH Support FR2 only. 4.1 Principle
PUCCH blanking Support FR1 only. 4.1 Principle
5 - 108
PUCCH Management
PUCCH Capacity Adaptation Management Support FR1 only. 6.1 Principle
3 Overview
For a description of the baseband physical layer of the 5G NR system, refer to Channel Management Overview.
4 PUCCH Basic Function
4.1 Principle
The PUCCH carries uplink control information to support uplink and downlink data transmission. Uplink Control Information (UCI) includes:
■ Scheduling Request (SR): requests UL-SCH resources from the gNodeB.
■ HARQ ACK or NACK: performs HARQ acknowledgement for the downlink data sent through the PDSCH.
■ Channel State Information (CSI): includes the CQI, PMI, and RI. It is used to notify the gNodeB of downlink channel quality to assist the
gNodeB in downlink scheduling.
The PUCCH supports three long formats (format 1, 3, 4) and two short formats (format 0, 2). You can set the
SRResource.srfmt,CSIReportResource.cSIfmt,ANResource.anFmt parameter on the UME to set the format. For the numbers of bits and required
symbols of these five formats, refer to Table 7. Currently, the number of symbols of format 1 is in the range of 4 to 14. The number of symbols of
format 3 and format 4 can only be 8, 12, or 14.The number of symbols of format 0 and format 2 can only be 1 or 2.
When intra-slot frequency hopping is configured for format1, format3, or format4, the first hop occupies half of the total number of symbols
(round down if the division is not complete), and the second hop occupies the remaining number of symbols.
Table 7 Formats Supported by the PUCCH
Format Number of OFDM Symbols Number of Bits
0 1-2 <= 2
1 4-14 <= 2
2 1-2 >2
3 4-14 >2
4 4-14 >2
For the long format, the number of bits of the UCI to be sent determines the control information carried in format 1, format3 or format 4. For
the control information supported by format 1, format 3 and format 4, refer to Table 8. The PUCCHFormat.simultaneousANandCSI parameter
can be set to send the AN and CSI at the same time. The only difference between the format3 and the format4 is that the format4 supports
code division multiplexing between users. Therefore, the format4 is scheduled preferentially.
For the short format, the number of bits of the UCI to be sent determines the control information carried in format 0 or format 2. For the control
information supported by format 0 or format 4, refer to Table 8. Currently, format0 and format2 only support ANs and SRs, and do not support
CSIs.
Table 8 Information Supported by the PUCCH in Different Formats
Format 0 Format 1 Format 2 Format 3 Format 4
Independent SR Independent SR Independent SR Independent CSI Independent CSI
1-bit AN 1-bit AN AN with more than two bits AN with more than two bits AN with more than two bits
2-bit AN 2-bit AN SR+AN with more than two SR+AN with more than two SR+AN with more than two bits
bits bits
SR+1-bit AN SR+1-bit AN SR+CSI SR+CSI
6 - 108
PUCCH Management
SR+2-bit AN SR+2-bit AN SR+CSI+AN with more than SR+CSI+AN with more than two
two bits bits
For format 1 with fourteen symbols, if different cyclic shifts and orthogonal sequences are allocated to a UE and intra-slot frequency hopping
(PUCCHFormat.intraslotFrequencyHopping) is disabled, an RB supports the coexistence of a maximum of 84 UEs (12 cyclic shifts and seven
orthogonal sequences) . If intra-slot frequency hopping (PUCCHFormat.intraslotFrequencyHopping) is enabled,an RB supports the coexistence
of 36 UEs (12 cyclic shifts and three orthogonal sequences) (diversity gain is added in this case) . To improve the demodulation performance of
the gNodeB, the isolation between UEs is increased during the actual scheduling.
Assume that in the FR1 TDD system, the frequency domain resource in format 1 is an RB,the start RB ID is 0, and the time domain occupies all
the 14 symbols of slot19. Figure 1 shows the time and frequency resources when intra-slot frequency
hopping(PUCCHFormat.intraslotFrequencyHopping) is disabled.
Figure 1 Resources in Format 1 When Intra-Slot Frequency Hopping Is Disabled
Figure 2 shows the time and frequency resources when intra-slot frequency hopping (PUCCHFormat.intraslotFrequencyHopping) is enabled.
Figure 2 Resources in Format 1 When Intra-Slot Frequency Hopping Is Enabled
For the number of data symbols of format 1, refer to Table 6.3.2.4.1-1 of 3GPP TS 38.211. For the number of pilot symbols, refer to Table
6.4.1.3.1.1-1 of 3GPP TS 38.211.
For format 3, in theory, 1~16 RBs can be occupied. The number of RBs must be a power product of 2, 3, and 5. Code division is not supported.
Based on the number of bits fed back by the UE, each UE occupies one or two RBs. When multiple UEs coexist, the UEs are distinguished in the
frequency domain. The additional DM-RS configuration affects the pilot location. For details, refer to Table 6.4.1.3.3.2-1 in the 3GPP 38.211
protocol.
Assume that in the FR1 TDD system, NRPhysicalCellDU.resourceExpansion is configured as false, intra-slot frequency hopping
(PUCCHFormat.intraslotFrequencyHopping) is disabled for format 3, and six RBs (RB243 to RB248) in the frequency domain and 14 symbols of
slot19 in the time domain are occupied. 【Figure Resources in Format 3 When intra-slot Frequency Hopping Is Disabled】 shows the time and
frequency resources. You can set the PUCCHFormat.additionalDMRS parameter on the UME to configure whether there are additional DM-RS.
7 - 108
PUCCH Management
Assume that intra-slot frequency hopping (PUCCHFormat.intraslotFrequencyHopping) is enabled for format 3, the first half hop occupies six
RBs (RB243 to RB248) in the frequency domain, the second half hop occupies six RBs (RB24 to RB29) in the frequency domain, and 14 symbols
of slot19 are occupied in the time domain. Figure 4 shows the time and frequency resources. You can set the PUCCHFormat.additionalDMRS
parameter on the UME to configure whether there are additional DM-RS.
For the number and position of pilot symbols in format 3, refer to Table 6.4.1.3.3.2-1 of 3GPP TS 38.211.
When there are multiple UEs at the same time, the format4 can multiplex the same time-frequency resources through code division
multiplexing. The resource occupation in the time domain is the same as that in format3. In the frequency domain, the difference with format3
lies in the number of occupied RB. Format4 always occupies one RB, while format3 can occupy 1~16 RBs.
For FR2 TDD, format0 occupies 1RB in the frequency domain and 1~2 symbols in the time domain. The format 2 can occupy can occupy 1~16
RBs in the frequency domain 1~2 symbols in the time domain. Format0 and format2 occupy one symbol by default. Frequency hopping is
supported when format0 and format2 PUCCH occupy two symbols in the time domain. Currently, format0 and format2 only support intra-slot
frequency hopping, which is controlled by PUCCHResCfg.freqHopping. When format0 and format2 occupy two symbols and the frequency
hopping switch (PUCCHResCfg.freqHopping) is enabled, intra-slot frequency hopping resources will be configured in the format0 and format2
PUCCH resource pools.
For the number of format 2 data symbols, refer to Table 6.3.2.5 A-1 and Table 6.3.2.5 A-2 in the 3GPP 38.211 protocol.
The following figure shows the format0 1RB and format2 2RB resources. The FR1 TDD system is used as an example. It is assumed that the
format 2 frequency domain resource includes two RBs, a start RB is zero, and a start symbol that occupies a slot19 in the PUCCH time domain
is 12.
For the format 0, when PUCCHResCfg.freqHopping is disabled, its time-frequency resources are shown in Figure 5 .
8 - 108
PUCCH Management
When PUCCHResCfg.freqHopping is enabled, its time-frequency resources are shown in Figure 6 .
For the format2, when PUCCHResCfg.freqHopping is disabled, its time-frequency resources are shown in Figure 7 .
When PUCCHResCfg.freqHopping is enabled, its time-frequency resources are shown in Figure 7 .
9 - 108
PUCCH Management
The eNodeB can switch between the MMSE-IRC receiver and the MMSE-MRC receiver by configuring the PUCCH IRC and MRC functions. By
default, the base station is configured with MRC. When interference exists, you can configure IRC to obtain the performance gain caused by
interference suppression. For details, refer to Receiver Management.
4.2 Network Analysis
Note:
The feature activation effect depends on the network environment. Therefore, this document only guides the feature provisioning. For network
gains pertinent contents, refer to ZTE for support.
4.2.1 Benefit Analysis
■ In a high-speed UE scenario, if the PUCCHFormat.additionalDMRS parameter is set to increase the density in the DMRS time domain, the
demodulation performance can be higher.

■ After intra-slot frequency hopping is configured, the demodulation gain of the PUCCH can be increased. Higher AN demodulation
capability can reduce the number of DL retransmissions and increase the downlink system capacity. Higher CSI demodulation
performance can help the gNodeB to obtain the optimal channel information.
4.2.2 Impact Analysis
None.
4.3 Application Scenarios
This feature is applicable to FR1/FR2 TDD and FR1 FDD systems.

For FR1 system, only Long PUCCH support.
For FR2 system, only Short PUCCH support.
4.4 Provisioning Guidance
4.4.1 PUCCH Provisioning Guidance
4.4.1.1 Prerequisites
Table 9 Hardware Requirement
Device Description Remark
5GC/EPC 5GC None
BBU V9200 None
AAU/RRU/Qcell No spectial requirement on RRU None
10 - 108
PUCCH Management
Table 10 Other Requirement
Other Requirement Description
CN None.
Carrier frequency bands, frequencies, and bandwidths None
UE None
Transmission bandwidth None
FTP server None
4.4.1.2 Restrictions
1.TNR BS PUCCH is enabled with frequency hopping, it is necessary to configure valid frequency hopping resource parameters; when non-
frequency hopping is configured, it is necessary to configure valid non-frequency hopping resource parameters.
2.The number of symbols configured for PUCCH resources must meet protocol requirements.
3.The PUCCH resource format should be configured under PUCCHFormat and the parameters should be matched.
4.PUCCH frequency resources cannot be overlapped with other channels.
5.NRPhysicalCellDU.pucchResShareSwch is set to false, the PUCCH spectrum of each BWP cannot overlap and exceed the BWP spectrum
range.
6.PUCCH channel resource coordination and allocation between different cells, RBAllocControl.pucchCellCoordAllocSwch when this function
is enabled, it is recommended that the multi-BWP PUCCH resource sharing function be enabled at the same time
NRPhysicalCellDU.pucchResShareSwch.
7.PUCCH resources are affected by the PUCCH adaptive switch nrphysicalcelldu.resourceexpansion.
4.4.1.3 Feature Activation
4.4.1.3.1 Feature Activation Process
The PUCCH Parameters involved as follow tables :
4.4.1.3.1.1 The FR1 TDD And FR1 FDD PUCCH Resource Parameters
When NRPhysicalCellDU.resourceExpansion is configured as false, the SRResource.rb4SR, ANResource.RbNum4A, and

CSIReportResource.userPeriod4CSI parameters determine the numbers of RBs occupied by different control information. When
NRPhysicalCellDU.resourceExpansion is configured as true, theSRResCfg.rb4SR, ANResCfg.Rb4AN , and
CSIRptResCfg.userPeriod4CSI parameters determine the numbers of RBs occupied by different control information. When
NRPhysicalCellDU.resourceExpansion is configured as false, the SRResource.sym4SR, SRResource.startSym4SR, ANResource.symNum4PerAN,
ANResource.startSym4AN, CSIReportResource.startSym4CSI and CSIReportResource.symNum4PerCSI parameters determine the number of
symbols occupied by different control information. The number of symbols of format 1, format3, and format 4 is 14 by default. When
NRPhysicalCellDU.resourceExpansion is configured as true, the SRResCfg.sym4SR,SRResCfg.startSym4SR,ANResCfg.symNum4PerAN ,
ANResCfg.startSym4AN, CSIRptResCfg.startSym4CSI and CSIRptResCfg.symNum4PerCSI parameters determine the number of symbols
occupied by different control information. The number of symbols of format 1, format3, and format 4 is 14 by default.
When NRPhysicalCellDU.resourceExpansion is configured as false, set ANResource.fmt4RBocc2scale to determine proportion of RB Numbers.
The value of this parameter indicates the proportion of the number of RBs of occ=2 to the number of format4 AN RB.Default setting is 10, which
means 100%.
When NRPhysicalCellDU.resourceExpansion is configured as true, set ANResCfg.fmt4RBocc2scale to determine proportion of RB Numbers. The
value of this parameter indicates the proportion of the number of RBs of occ=2 to the number of format4 AN RB. Default setting is 10, which
11 - 108
PUCCH Management
means 100%.
When NRPhysicalCellDU.resourceExpansion is configured as false, set the CSIReportResource.multiplePeriodCoeff4CQI,
CSIReportResource.multiplePeriodCoeff4RSRP, and CSIReportResource.multiplePeriodCoeff4PMI parameters to determine the CSI
transmission period.
When NRPhysicalCellDU.resourceExpansion is configured as true, configure CSIRptResCfg.trPeriod4CSI,
CSIRptResCfg.multiplePeriodCoeff4CQI, CSIRptResCfg.multiplePeriodCoeff4RSRP and CSIReportResource.multiplePeriodCoeff4PMI to
determine the CSI transmission period.
When NRPhysicalCellDU.resourceExpansion is configured as false, set SRResource.tranPeriod4SR to determine the SR transmission period.
When NRPhysicalCellDU.resourceExpansion is configured as true, set SRResCfg.tranPeriod4SR to determine the SR transmission period.
Currently, the FR1 FDD only supports format1 and format3.
Table 11 FR1 TDD PUCCH physical resource management parameters
No Step Related Parameter Process Verification
1 Confirm whether to turn on NRPhysicalCellDU.resourceExpansion None

PUCCH resource adaptation
switch
2 Confirm whether to open PUCCHFormat.simultaneousANandCSI None

PUCCH AN and CSIRS
simultaneous interpreting
function
N0 Step Enable PUCCH Resource Disable PUCCH Resource Process Verification

Adaptation Adaptation
3 Confirm whether to turn on PUCCHResCfg.freqHopping PUCCHConfig.intraslotFrequency

PUCCH frequency hopping Hopping
function
4 PUCCH SR resource SRResCfg.rb4SR SRResource.rb4SR None

configuration
SRResCfg.deltaCHfmt SRResource.deltaCHfmt None
SRResCfg.tranPeriod4SR SRResource.tranPeriod4SR None
5 PUCCH AN resource ANResCfg.deltaCHfmt ANResource.deltaCHfmt None

configuration
ANResCfg.Rb4AN ANResource.RbNum4AN None
6 PUCCH CSI resource CSIRptResCfg.rbNum4CSI CSIReportResource.rbNum4CSI

configuration
CSIRptResCfg.trPeriod4CSI CSIReportResource.trPeriod4CSI None
CSIRptResCfg.multiplePeriodCoef CSIReportResource.multiplePerio None

f4CQI dCoeff4CQI

f4RSRP dCoeff4RSRP

f4PMI dCoeff4PMI
4.4.1.3.1.2 The FR2 TDD PUCCH Resource Parameters

Table 12 FR2 TDD PUCCH physical resource management parameters
No Step Related Parameter
1 PUCCH Feedback delay PUCCHConfig.dlDataToULACK
2 longPUCCH\shortPUCCH PUCCHConfig.longPUCCHorShortPUCCH
Switch
3 PUCCH fmt0 Power offset PUCCHPowerControl.deltaFPUCCHf0
12 - 108
PUCCH Management
4 PUCCH fmt2 Power offset PUCCHPowerControl.deltaFPUCCHf2
4.4.1.3.2 Related Parameters and Figures
4.4.1.3.2.1 The FR1 TDD PUCCH Resouce Feature Activation
According to the network management configuration in the current version, the PUCCH format1 / format3 configuration has been enabled by
default. Here, the mutual switching between format3 / format4 is described;
Due to the merges of PUCCH adaptation and fixed gear parameter decoupling adaptation requirements, the resource table configured by
PUCCH will be affected by the PUCCH resource adaptation switch NRPhysicalCellDU.resourceExpansion (false by default):
When the NRPhysicalCellDU.resourceExpansion is false，The configuration resource table of PUCCH is：
SRResource，CSIReportResource，ANResource
When the NRPhysicalCellDU.resourceExpansion is true，The configuration resource table of PUCCH is：SRResCfg，CSIRptResCfg，ANResCfg
PUCCH format3 Resource is Active default; when PUCCH format4 should be active , it should be:
modify the PUCCHConfig.maxPayloadMinus1 to 256;256
modify the CSIRptResCfg.rbNum4AN and CSIRptResCfg.rbNum4CSI to the nonzero value
PUCCH physical resource network management path of Ume：

ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > resourceExpansion
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig > PUCCHFormat
【Resource List 1】
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig >PUCCHResCfg > SRResCfg
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig >PUCCHResCfg > ANResCfg
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig > PUCCHResCfg >CSIRptResCfg
【Resource List 2】
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig >SRResource
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig >CSIReportResource
ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhyResourceConfigforBWPUL > PUCCHConfig >ANResource
When the NRPhysicalCellDU.resourceExpansion is false，the Resource Lsit1: SRResource，CSIReportResource，ANResource is in active：
Table 13 PUCCH physical resource management feature activation when resourceExpansion is false
No. Paramete Parameter N Configuration Exampl Parameter Path

r ID ame e
1 NRPhysic Switch of false Managed Element/NRRadioInfrastructure/NRPhysicalCellDU

alCellDU. resource
resource expansion
Expansio
n
13 - 108
PUCCH Management
2 PUCCHC Maximum 80;256 Managed

onfig.ma number of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
xPayload bits fed back configuration
Minus1
3 PUCCHC Intra-slot disabled[disabled] Managed

onfig.intr frequency Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
aslotFreq hopping configuration
uencyHo
switch
pping
4 PUCCHC PUCCH frame longPUCCH[1] Managed

onfig.lon format Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
gPUCCHo configuration
rShortPU
CCH
5 PUCCHC Switch of CQI false[false] Managed

onfig.cqi reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ReportEn configuration
able
6 PUCCHC RSRP false[false] Managed

onfig.rsrp reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ReportEn switch configuration
able
7 PUCCHC PMI reporting true[true] Managed

onfig.pmi switch Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
able
14 - 108
PUCCH Management
8 PUCCHFo PUCCH format3[format3] Managed

rmat.puc format Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
chFormat configuration/PUCCH format
9 PUCCHFo Switch of true Managed

rmat.sim simultaneous Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ultaneou CSI and AN configuration/PUCCH format
sANandC
transmission
SI
10 PUCCHFo Maximum bit zeroDot35[zeroDot35] Managed

rmat.max rate Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
CodeRate configuration/PUCCH format
11 SRResour Number of 2 Managed

ce.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
for SR configuration/SRResourcePool
transmission
12 SRResour Code 2[2] Managed

ce.deltaC channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
Hfmt interval configuration/SRResourcePool
13 SRResour SR 10;10;10;10 Managed

ce.tranPe transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
riod4SR period configuration/SRResourcePool
14 ANResou Code 2[2] Managed

rce.delta channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
CHfmt interval configuration/AN resource pool
15 ANResou Number of 8 Managed

rce.RbNu PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
m4AN for AN configuration/AN resource pool
transmission
15 - 108
PUCCH Management
16 CSIRepor Number of 8 Managed

tResourc RBs in a CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
e.userPer reporting configuration/CSIResourcePool
iod4CSI
period
17 CSIRepor CSI reporting 20 Managed

tResourc period Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
e.trPerio configuration/CSIResourcePool
d4CSI
18 CSIRepor CQI period 2 Managed

tResourc multiple Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
e.multipl coefficient configuration/CSIResourcePool
ePeriodC
oeff4CQI
16 - 108
PUCCH Management
19 CSIRepor RSRP period 2 Managed

ePeriodC
oeff4RSR
P
17 - 108
PUCCH Management
20 CSIRepor PMI period 1 Managed

ePeriodC
oeff4PMI
When the NRPhysicalCellDU.resourceExpansion is true，the Resource Lsit 2: SRResource，CSIReportResource，ANResource is in active：
Table 14 PUCCH physical resource management feature activation when resourceExpansion is true
No. Paramete Parameter N Configuration Exampl Parameter Path

r ID ame e
1 NRPhysic Switch of true Managed Element/NRRadioInfrastructure/NRPhysicalCellDU

alCellDU. resource
resource expansion
Expansio
n

Minus1
18 - 108
PUCCH Management

uencyHo
switch
pping
4 PUCCHR Frequency disabled[disabled] Managed

esCfg.fre hopping Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
qHopping configuration/Configuration for PUCCH resource adaptation
5 PUCCHC PUCCH frame longPUCCH[1] Managed

onfig.lon format Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
gPUCCHo configuration
rShortPU
CCH
6 PUCCHC Switch of CQI false[false] Managed

onfig.cqi reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
able
7 PUCCHC RSRP false[false] Managed

onfig.rsrp reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ReportEn switch configuration
able
8 PUCCHC PMI reporting true[true] Managed

onfig.pmi switch Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
able
9 PUCCHFo PUCCH format3[format3] Managed

rmat.puc format Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
chFormat configuration/PUCCH format
10 PUCCHFo Switch of true Managed

rmat.sim simultaneous Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ultaneou CSI and AN configuration/PUCCH format
sANandC
transmission
SI
11 PUCCHFo Maximum bit zeroDot35[zeroDot35] Managed

rmat.max rate Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
12 SRResCfg Number of 2 Managed

.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
for SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
transmission
19 - 108
PUCCH Management
13 SRResCfg Code 3[3] Managed

.deltaCHf channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
mt interval configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
14 SRResCfg SR 10;10;10;10 Managed

.tranPeri transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
od4SR period configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
15 ANResCfg Code 3[3] Managed

mt interval configuration/Configuration for PUCCH resource adaptation/AN resource pool
16 ANResCfg Number of 8 Managed

.Rb4AN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
for AN configuration/Configuration for PUCCH resource adaptation/AN resource pool
transmission
17 CSIRptRe Number of 2 Managed

sCfg.rbN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
um4CSI for CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
reporting
18 CSIRptRe CSI reporting 20 Managed

sCfg.trPer period Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
iod4CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
19 CSIRptRe CQI period 2 Managed

sCfg.mult multiple Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
iplePerio coefficient configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
dCoeff4C
QI
20 - 108
PUCCH Management
20 CSIRptRe RSRP period 2 Managed

dCoeff4R
SRP
21 CSIRptRe PMI period 1 Managed

dCoeff4P
MI
Table 15 PUCCH Parameter feature activation 1
No. Parameter I Paramete Configura Parameter Path Configuration Principle

D r Name tion Exa
mple
21 - 108
PUCCH Management
1 NRPhysical Switch of false Managed The parameter is configured based

CellDU.reso resource Element/NRRadioInfrastructure/NRPhysicalCellDU on the number of UEs in the existing
urceExpansi expansion network. When the number of UEs
on
exceeds the configured capacity, set
this parameter to true; otherwise, set
this parameter to false.
PUCCH resource adaptive switch，false is default：

When the NRPhysicalCellDU.resourceExpansion is false，The configuration resource table of PUCCH is：
SRResource，CSIReportResource，ANResource
When the NRPhysicalCellDU.resourceExpansion is true，The configuration resource table of PUCCH is：SRResCfg，CSIRptResCfg，ANResCfg
Figure 9 PUCCH Physical Resource Management Feature Active 1
When the NRPhysicalCellDU.resourceExpansion is true:
No. Paramete Parameter N Configurati Parameter Path Configuratio

r ID ame on Exampl n Principle
e
22 - 108
PUCCH Management
1 SRResCfg Number of 2 Managed To support a

.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH large
for SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool number of
transmission RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
number of
available
RBs on the
PUSCH and
the uplink
peak rate to
decrease.
2 SRResCfg Code 3[3] Managed The

.deltaCHf channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
mt interval configuration/Configuration for PUCCH resource adaptation/SRResCfgPool value is
determined
based on the
simulation
performance
of the
physical
layer. If this
parameter is
set to a
larger value,
the SR
interference
between
UEs can be
reduced.
However,
the number
of available
SR resources
becomes
smaller.
23 - 108
PUCCH Management
3 SRResCfg SR 10;10;10;10 Managed To support a

.tranPeri transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH large
od4SR period configuration/Configuration for PUCCH resource adaptation/SRResCfgPool number of
RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
latency to
increase.
When the NRPhysicalCellDU.resourceExpansion is false：
No. Paramete Parameter N Configurati Parameter Path Configuration

r ID ame on Exampl Principle
e
1 SRResour Number of 2 Managed This

ce.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
for SR configuration/SRResourcePool should set
transmission based on the
number of
connected
RRC UEs
supported by
the system.
The larger the
number of
connected
RRC UEs is, the
larger the
parameter
value is.
2 SRResour Code 2[2] Managed The parameter

ce.deltaC channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH value should
Hfmt interval configuration/SRResourcePool be modified
based on the
PUCCH
simulation
performance
of the physical
layer. It is not
recommended
that the
parameter
value be
modified.
3 SRResour SR 10;10;10;10 Managed Null

Note: PUCCH format3/format4 need to modify parameters with the corresponding format
24 - 108
PUCCH Management
when the resourceExpansion is true , please config the SRResCfg:
when the resourceExpansion is false , please config the SRResouce:
25 - 108
PUCCH Management
No. Paramete Parameter N Configura Parameter Path Configurati

r ID ame tion Exa on Principle
mple
1 ANResCfg Code 3[3] Managed If serious

.deltaCHf channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH interference
mt interval configuration/Configuration for PUCCH resource adaptation/AN resource pool exists
between
code
channels in
AN PUCCH
format1,
the ratio of
downlink
DTX
becomes
high. In this
case, set
this
parameter
to a larger
value.
2 ANResCfg Number of 8 Managed This

.Rb4AN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
for AN configuration/Configuration for PUCCH resource adaptation/AN resource pool is
transmission configured
in
accordance
with the
actual
service
type.
When the NRPhysicalCellDU.resourceExpansion is false:
No. Paramete Parameter N Configura Parameter Path Configuration

r ID ame tion Exa Principle
mple
1 ANResou Code 2[2] Managed The parameter

rce.delta channel Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH value should
CHfmt interval configuration/AN resource pool be modified
based on the
PUCCH
simulation
performance of
the physical
layer. It is not
recommended
that the
parameter
value be
modified.
26 - 108
PUCCH Management
2 ANResou Number of 8 Managed The larger the

rce.RbNu PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH number of
m4AN for AN configuration/AN resource pool downlink UEs
transmission that may be
scheduled in
each binding
window is, the
larger the
parameter
value is
recommended.
Format3：
when the resourceExpansion is true , please config the ANResCfg:
when the resourceExpansion is true , please config the ANResource:
27 - 108
PUCCH Management
Format4：
when the resourceExpansion is true , please config the ANResCfg:
when the resourceExpansion is false , please config the ANResource:
28 - 108
PUCCH Management
No. Paramete Parameter Configura Parameter Path Configuration

r ID Name tion Exa Principle
mple
1 CSIRptRe Number 8 Managed This

sCfg.rbN of PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
um4CSI RBs for configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool configured in
CSI accordance
reporting with the
actual service
type.
29 - 108
PUCCH Management
2 CSIRptRe CSI 20 Managed This

sCfg.trPer reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
iod4CSI period configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool should be
configured
based on user
experience
and UE access
capacity. The
larger the
value of an
element is, the
more the
corresponding
UEs are
supported.
The smaller
the value of an
element is, the
fewer the
corresponding
UEs are
supported.
3 CSIRptRe CQI 2 Managed This

sCfg.mult period Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
iplePerio multiple configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool configured in
dCoeff4C
coefficient accordance
QI
with the
required CQI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
30 - 108
PUCCH Management
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
CQI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
4 CSIRptRe RSRP 2 Managed This

dCoeff4R
SRP
with the
required RSRP
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
31 - 108
PUCCH Management
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
RSRP
reporting
period
calculated
through
configuration
32 - 108
PUCCH Management
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
5 CSIRptRe PMI 1 Managed This

dCoeff4P
MI
with the
required PMI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
33 - 108
PUCCH Management
the RSRP
period
multiple
coefficient is
to 1, then, the
PMI reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
PMI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
When the NRPhysicalCellDU.resourceExpansion is false:
No. Paramete Parameter Configura Parameter Path Configuration

r ID Name tion Exa Principle
mple
34 - 108
PUCCH Management
1 CSIRepor Number 8 Managed This

tResourc of PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
e.rbNum RBs for configuration/CSIResourcePool should set
4CSI
CSI based on the
reporting number of
connected
RRC UEs
supported by
the system.
The larger the
number of
connected
RRC UEs is,
the larger the
parameter
value is. To
support more
UEs in the cell,
increase the
parameter
value.
2 CSIRepor CSI 20 Managed This

tResourc reporting Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
e.trPerio period configuration/CSIResourcePool should be
d4CSI
configured
based on user
experience
and UE access
capacity. The
larger the
value of an
element is, the
more the
corresponding
UEs are
supported.
The smaller
the value of an
element is, the
fewer the
corresponding
UEs are
supported.
3 CSIRepor CQI 2 Managed This

tResourc period Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
e.multipl multiple configuration/CSIResourcePool configured in
ePeriodC
oeff4CQI
with the
required CQI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
35 - 108
PUCCH Management
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
CQI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
36 - 108
PUCCH Management
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
4 CSIRepor RSRP 2 Managed This

ePeriodC
oeff4RSR
with the
P
required RSRP
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
37 - 108
PUCCH Management
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
RSRP
reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
5 CSIRepor PMI 1 Managed This

ePeriodC
oeff4PMI
with the
required PMI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
38 - 108
PUCCH Management
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
PMI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
Format3：
when the resourceExpansion is true , please config the CSIRptResCfg:
39 - 108
PUCCH Management
when the resourceExpansion is false , please config the CSIReportResource:
Format4：
when the resourceExpansion is true , please config the CSIRptResCfg:
40 - 108
PUCCH Management
when the resourceExpansion is false , please config the CSIReportResource:
4.4.1.3.2.2 The FR1 FDD PUCCH Resouce Feature Activation
Path：
NRRadioInfrastructure->NRPhysicalCellDU->PhyResourceConfigforBWPUL->PUCCHConfig->SRResource
41 - 108
PUCCH Management
NRRadioInfrastructure->NRPhysicalCellDU->PhyResourceConfigforBWPUL->PUCCHConfig->CSIReportResource
NRRadioInfrastructure->NRPhysicalCellDU->PhyResourceConfigforBWPUL->PUCCHConfig->ANResource
NRRadioInfrastructure->NRPhysicalCellDU->PhyResourceConfigforBWPUL->PUCCHConfig->PUCCHFormat
Table 22 FR1 FDD PUCCH Physical Resource Management Feature Activation
No. Paramete Parameter N Configurat Parameter Path Configuration

r ID ame ion Examp Principle
le
1 ANResou Number of 1 Managed The larger the

rce.RbNu PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH number of
m4AN for AN configuration/AN resource pool downlink UEs
transmission that may be
scheduled in
each binding
window is, the
larger the
parameter
value is
recommended.
2 ANResou Start symbol sym0 Managed In common

rce.startS of the AN Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH scenarios, use
ym4AN PUCCH configuration/AN resource pool the default
value. In short-
delay
scenarios, set
this parameter
to the
corresponding
start symbol.
The start
symbol of the
AN is used
together with
the number of
the symbols of
the AN. The
more the
symbols, the
lower the AN
bit rate, and
the better the
demodulation
performance.
42 - 108
PUCCH Management
3 ANResou Number of 13 Managed If the AN

rce.symN symbols per Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH PUCCH
um4PerA PUCCH for configuration/AN resource pool resources are
N
AN configured at
transmission the slot level,
this parameter
includes 1
element, and
the parameter
value is
determined by
the number of
uplink symbols
of the slot
where the AN
PUCCH
resources are
located. If the
AN PUCCH
resources are
configured at
the subslot
level, this
parameter
includes more
than 1
element. The
parameter
value is
determined by
the length of
the subslot.
4 CSIRepor Number of 2 Managed This parameter

tResourc PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH should set
e.rbNum for CSI configuration/CSIResourcePool based on the
4CSI
reporting number of
connected RRC
UEs supported
by the system.
The larger the
number of
connected RRC
UEs is, the
larger the
parameter
value is. To
support more
UEs in the cell,
increase the
parameter
value.
43 - 108
PUCCH Management
5 CSIRepor Start symbol 0 Managed The current

tResourc of the CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH version does
e.startSy PUCCH configuration/CSIResourcePool not support
m4CSI
typeB resource
allocation of
the PUSCH.
The parameter
value can only
be 0 and
cannot be
modified.
6 CSIRepor Number of 13 Managed If the CSI

tResourc PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH PUCCH
e.symNu symbols for configuration/CSIResourcePool resources are
m4PerCS
CSI reporting configured at
I
the slot level,
this parameter
includes 1
element, and
the parameter
value is
determined by
the number of
uplink symbols
of the slot
where the CSI
PUCCH
resources are
located. If the
CSI PUCCH
resources are
configured at
the subslot
level, this
parameter
includes more
than 1
element. The
parameter
value is
determined by
the length of
the subslot.
44 - 108
PUCCH Management
7 PUCCHFo Intra-slot enable Managed This parameter

rmat.intr frequency Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH should be
aslotFreq hopping configuration/PUCCH format configured
uencyHo
switch based on the
pping
actual
scenario. If it is
set to
"enabled", the
anti-
interference
capability of
the PUCCH can
be improved. If
the false
detection rate
of downlink
DTX or uplink
SR resources is
high and intra-
timeslot
frequency
hopping is
enabled, the
false detection
rate of
downlink DTX
or uplink SR
resources can
be significantly
reduced. It is
recommended
that this
parameter be
set to
"enabled".
Otherwise, set
this parameter
to "disabled"
to obtain
higher PUSCH
peak traffic.
45 - 108
PUCCH Management
8 PUCCHFo PUCCH format3 Managed The parameter

rmat.puc format Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH value should
chFormat configuration/PUCCH format be selected
based on the
PUCCH format
supported by
the current
frame structure
and the
number of bits
carried. For 1
to 2 bits, set
this parameter
to "format0" or
"format1"; for
more than 2
bits, set this
parameter to
"format2",
"format3", or
"format4".
9 PUCCHFo Switch of TRUE Managed If the PUCCH

rmat.sim simultaneous Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH performance
ultaneou CSI and AN configuration/PUCCH format degrades
sANandC
transmission significantly
SI
due to
simultaneous
transmission of
the AN and CSI,
set this
parameter to
"Close".
10 SRResour Number of 1 Managed This parameter

ce.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH should set
for SR configuration/SRResourcePool based on the
transmission number of
connected RRC
UEs supported
by the system.
The larger the
number of
connected RRC
UEs is, the
larger the
parameter
value is.
11 SRResour Start symbol 0 Managed The current

ce.startS of the SR Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH version does
ym4SR PUCCH configuration/SRResourcePool not support
typeB of the
PUSCH. The
parameter
value can only
be 0 and
cannot be
modified.
46 - 108
PUCCH Management
12 SRResour Number of 13 Managed If the SR

ce.sym4S PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH PUCCH
R symbols for configuration/SRResourcePool resources are
SR configured at
transmission the slot level,
this parameter
includes 1
element, and
the parameter
value is
determined by
the number of
uplink symbols
of the slot
where the SR
PUCCH
resources are
located.If the
SR PUCCH
resources are
configured at
the subslot
level, this
parameter
includes more
than 1
element. The
parameter
value is
determined by
the length of
the subslot.
13 SRResour SR 10 Managed Null

14 CSIRepor CSI reporting [20;40;160] Managed This parameter

tResourc period Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH should be
e.trPerio configuration/CSIResourcePool configured
d4CSI
based on user
experience and
UE access
capacity. The
larger the value
of an element
is, the more the
corresponding
UEs are
supported. The
smaller the
value of an
element is, the
fewer the
corresponding
UEs are
supported.
Figure 20 FR1 FDD PUCCH Parameter Configuration 1
47 - 108
PUCCH Management
48 - 108
PUCCH Management
Table 23 FR2 TDD PUCCH Physical Resource Management Feature Activation
No. Paramete Parameter N Configuration Ex Parameter Path

r ID ame ample
49 - 108
PUCCH Management
1 PUCCHC Feedback 2;3;5 Managed

onfig.dlD delay Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
ataToULA configuration
CK
2 PUCCHC PUCCH shortPUCCH Managed

onfig.lon frame Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
gPUCCHo format configuration
rShortPU
CCH
50 - 108
PUCCH Management
3 PUCCHP Power offset -3 Managed

owerCon for PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
trol.delta Format 0 configuration/PUCCHPowerControl
FPUCCHf
relative to
0
PUCCH
reference
power
4 PUCCHP Power offset 6 Managed

owerCon for PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
trol.delta Format 2 configuration/PUCCHPowerControl
FPUCCHf
relative to
2
PUCCH
reference
power
5 PUCCHFo Maximum zeroDot35 Managed

rmat.max bit rate Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
6 SRResCfg PUCCH format0[format0] Managed

.srfmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
transmission
51 - 108
PUCCH Management
7 CSIRptRe PUCCH format2[format2] Managed

sCfg.cSIf format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
mt CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
reporting
8 ANResCfg PUCCH format2[format2] Managed

.anckFmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
AN configuration/Configuration for PUCCH resource adaptation/AN resource pool
transmission
9 ANResCfg PUCCH format0[format0] Managed

.anckFmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
AN configuration/Configuration for PUCCH resource adaptation/AN resource pool
transmission
10 ANResCfg Start symbol sym12[sym12] Managed

.startSym of the AN Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
4AN PUCCH configuration/Configuration for PUCCH resource adaptation/AN resource pool
52 - 108
PUCCH Management
11 SRResCfg Number of 2 Managed

.rb4SR PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
for SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
transmission
12 SRResCfg Code 2[2] Managed

mt interval configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
13 SRResCfg SR 160 Managed

.tranPeri transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
od4SR period configuration/Configuration for PUCCH resource adaptation/SRResCfgPool
53 - 108
PUCCH Management
14 ANResCfg Code 2[2] Managed

mt interval configuration/Configuration for PUCCH resource adaptation/AN resource pool

transmission

transmission

sCfg.rbN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
um4CSI for CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
reporting
The Following Figure shows the parameters to be configured and their default values when the high frequency PUCCH function is enabled. At
present, high frequency only supports short-pucch。
Figure 24 FR2 TDD PUCCH Parameter Configuration 1
54 - 108
PUCCH Management
55 - 108
PUCCH Management
4.4.1.4 Feature Deactivation
The PUCCH format3 Feature is turned on by default;

The PUCCH format4 Feature turned off is describle as follow:
Table 24 FR1 TDD PUCCH Fomat4 Physical Resource Management Feature deactivation
No. Paramete Parameter N Configuration Exa Parameter Path

r ID ame mple
56 - 108
PUCCH Management

Minus1

sCfg.user RBs in a CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
Period4C reporting configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
SI
period

transmission
4 CSIRepor Number of 0 Managed

tResourc RBs in a CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
e.userPer reporting configuration/CSIResourcePool
iod4CSI
period

transmission

uencyHo
switch
pping
Table 25 FR1 TDD PUCCH Parameter Feature deactivation 1
No. Parameter Parameter Configura Parameter Path

ID Name tion Exam
ple
1 PUCCHCon Maximum 80;256 Managed

fig.maxPay number of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
loadMinus bits fed configuration
1
back
Figure 29 PUCCH Physical Resource Management Feature deactivation 1
57 - 108
PUCCH Management
No. Parameter Parameter Configura Parameter Path

ID Name tion Exa
mple
1 CSIRptRes Number of 0 Managed

Cfg.userPe RBs in a CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
riod4CSI reporting configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool
period
2 CSIReport Number of 0 Managed

Resource.u RBs in a CSI Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH
serPeriod4 reporting configuration/CSIResourcePool
CSI
period
Note: the numbers of RB in both CSIReportResource and CSIRptCfg in pucch Format4 should be configured to 0
58 - 108
PUCCH Management
No. Paramete Parameter Configura Parameter Path

r ID Name tion Exa
mple

transmission

transmission
Note:the numbers of RB in both ANResource and ANCfg in pucch Format4 should be configured to 0
59 - 108
PUCCH Management
Figure 32 FR1 TDD PUCCH Parameter Feature deactivation 4
No. Parameters Values
1 PUCCHConfig.intraslotFrequencyHopping 0
60 - 108
PUCCH Management
4.4.1.5 Test Method
Table 28 PUCCH Resources Feature Test Method
Test Item PUCCH Resources Feature Test Method
Sub-item N/A
Prerequisites 1、when the resourceExpansion is false，Configure PUCCH format3 / format4 according to

Table 29 PUCCH physical resource management feature activation when resourceExpansion is
false
2、when the resourceExpansion is true，Depend on the【Table PUCCH physical resource
management feature Parameters when resourceExpansion is true】to configure PUCCH
Format3/Format4 Resource.
2、Cell is Active
Test Steps 1、Ue attached Cell successfully.

2、Observe the PUCCH-config signaling message carried by the RRCReconfiguration message of
the terminal
Expected Result Ue attached Cell successfully,PUCCH-config signaling message carried by the RRCReconfiguration
message of the terminal.the detail result shows in 4.4.1.6
4.4.1.6 Provisioning Observation
4.4.1.6.1 FR1 TDD PUCCH Resource Provisioning verification
The Cell is normal and UE can access the cell successfully.

PUCCH configuration is deliveried to UE through RRC connection Reconfiguration. the log path of Qualcomm mobile is as follows:：QXDM >
Filtered View > RRCConnectionReconfiguration，
the KeyWord :pucch-Config setup。
61 - 108
PUCCH Management
Figure 35 The FR1 TDD PUCCH Resource Provisioning Verification
4.4.1.6.1.1 FR1 FDD PUCCH Resource Provisioning Verification

PUCCH configuration is deliveried to UE through RRC connection Reconfiguration,the KeyWord :pucch-Config setup。
Figure 36 The FR2 FDD PUCCH Resource Provisioning Verification
4.4.1.6.1.2 FR2 TDD PUCCH Resource Provisioning Verification
62 - 108
PUCCH Management

PUCCH configuration is deliveried to UE through RRC connection Reconfiguration. the log path of Qualcomm mobile is as follows:：QXDM >
Filtered View > RRCConnectionReconfiguration，
the KeyWord :pucch-Config setup。
Figure 37 The FR2 TDD PUCCH Resource Provisioning Verification
4.4.2 PUCCH IRC Provisioning Guidance
63 - 108
PUCCH Management
5GC/EPC 5GC None
BBU V9200 None
CN None.
UE None
FTP server None
None
4.4.2.3.1.1 The FR1 TDD PUCCH Resource Parameters
Table 32 FR1 TDD PUCCH IRC management parameters
No Step Related Parameter
1 Confirm whether to turn on PhysCommon.pucchIrcSwch

PUCCH IRC switch
According to the network management configuration in the current version, the PUCCH IRC is usually closed . Here, how to enable PUCCH IRC
is described;
PUCCH IRC network management path of Ume：

ManagedElement > NRRadioInfrastructure > NRPhysicalCellDU > PhysCommon
Table 33 PUCCH IRC management feature activation
64 - 108
PUCCH Management
No. Parameter ID Paramete Configuratio Parameter Path Configuration P

r Name n Example rinciple
1 PhysCommon.p PUCCH Open[1] Managed When uplink

ucchIrcSwch IRC Element/NRRadioInfrastructure/NRPhysicalCellDU/PhysCommon interference
switch exists, set this
parameter to 1
(Open).
Figure 38 PUCCH Physical Resource Management Feature Active
The PUCCH IRC Feature turned off is describle as follow:
Table 34 PUCCH IRC Management Feature deactivation
No. Parameter ID Parameter Na Configuration Exa Parameter Path

me mple
1 PhysCommon.pucchIrc PUCCH IRC Close[0] Managed

Swch switch Element/NRRadioInfrastructure/NRPhysicalCellDU/PhysCommon
Figure 39 PUCCH IRC Management Feature deactivation
65 - 108
PUCCH Management
4.4.2.5 Test Method
Table 35 PUCCH IRC Feature Test Method
Test Item PUCCH IRC Feature Test Method
Sub-item N/A
Prerequisites 1、Cell is Active
Test Steps 1、View the value of gptMccCellInfoDdr->atMccCellInfo[0]->cellCfg->PUCCHMatrixType through the

JDspMonitor
2、Ue attached Cell successfully.
Expected Result 1、PUCCHMatrixType=1

2、Ue attached Cell successfully.
4.4.2.6.1 FR1 TDD PUCCH Resource Provisioning verification

MCC cell parameters：gptMccCellInfoDdr->atMccCellInfo[0]->cellCfg->PUCCHMatrixType=1。
Figure 40 The PUCCH IRC Provisioning Verification
66 - 108
PUCCH Management
5 PUCCH Format3 Dynamic Preemption
5.1 Principle
According to the scheduling situation of the downlink PDSCH, the idle PUCCH Format3 RBs are used for scheduling the PUSCH to improve the
uplink traffic. The function enabling switch is RBAllocControl.rbShareSwitch4ANf3f4andPUSCH. The flow is as follows:
Figure 41 PUCCH Format3 Dynamic PremPtion
Step Step Description
1 If the PUCCH Format3 dynamic preemption function is enabled (RBAllocControl.rbShareSwitch4ANf3f4andPUSCH is set to

Open)), the downlink PDSCH scheduling information will be obtained.
67 - 108
PUCCH Management
2 The parameter AN Format3, Format4 and PUSCH RB share part RBs (PUCCHConfig.extraANResRBRatio). The RBs of Format3 are
divided into two parts: Non-share part and share part. According to the estimated PDSCH scheduling, all RBs of AN Format3 will
be preempted or only the RBs of Format3 will be preempted.
3 On the RB bitmap of the available RBs on the PUSCH, update the RBs of the unused PUCCH Format3 as available.
Note:
The use of idle PUCCH Foramt3 RBs can increase the available RBs of the uplink PUSCH and increase the uplink traffic to improve user
experience.
None.
When uplink traffic is high and downlink traffic is low, uplink traffic is increased to improve user experience.
5.4.1 PUCCH Format3 dynamic preemption feature provisioning guidance
5.4.1.1 Operation Requirements
Table 36 Hardware Requirements
Device Name Type Description Remarks
5GC or EPC 5GC or EPC None
BBU V9200 (V3C small antenna not supported) None
AAU, RRU, or Qcell No special requirements for RF units None
Table 37 Other Requirements
Associated Item Correlation Requirements
Core network There are no special requirements
Carrier Frequency Band, Frequency Point, and Bandwidth There are no special requirements
Terminal There are no special requirements
Transmission bandwidth There are no special requirements
FTP server There are no special requirements
5.4.1.2 Usage Restrictions
1 Supporting TNR 2.5 ms dual, 5 ms single, 2.5 ms single (DDDSU), 2.5 ms single (DSUUU) frame structure;
2 When the minimum K1 >=3, only 2.5 ms dual, 2.5 ms single (DDDSU) and 2.5 ms single (DSUUU) are supported;
3 This function does not take effect when CA UE is available.有CA UE时该功能不⽣效；
68 - 108
PUCCH Management
5.4.1.3.1 Commissioning Steps
Table 38 PUCCH Format3 Dynamic Preemption Function Parameter List
No Step Related Parameter Process Verific

ation
1 Confirm whether to enable the switch for sharing RB resources AN RBAllocControl.rbShareSwitch4ANf3f4

format3, 4 and PUSCH andPUSCH
2 Confirm the RB ratio of the shared AN format3/4 PUCCHConfig.extraANResRBRatio
Taking the TNR 100M 5ms single frame structure as an example, configure it according to the current version of the UME system.
The dynamic preemption RB switch of AN format3 and 4 is disabled by default, which is close. The ratio of RBs of the shared AN format3/4 is
[75: 0: 0] by default. Change the dynamic preemption RB switch of AN format3 and 4 to open. After the cell is reset, the function takes effect.
Table 39 Activation Of Dynamic Preemption Function PUCCH Format3
No. Paramete Paramete Configura Parameter Path Configuration

r ID r Name tion Exa Principle
mple
1 RBAllocC Switch of open Managed Element/NRRadioInfrastructure/NRPhysicalCellDU/RB Alloc Control If the required

ontrol.rb sharing number of RBs
ShareSwi RBs of AN of AN format3
tch4ANf3f
format3 and AN
4andPUS
and AN format4 at
CH
format4 peak periods
with the differs greatly
PUSCH from that at
idle periods in
the cell, it is
recommended
that this
parameter be
set to 1
(Open), so as
to increase the
uplink traffic
when few RBs
of AN format3
and AN
format4 are
required.
69 - 108
PUCCH Management
2 PUCCHC Ratio of 【75： Managed When it is

onfig.extr the RBs 0：0】 Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH allowed to
aANResR of AN configuration share RBs of
BRatio
format3 AN format3
and AN and AN
format4 format4 with
shared the PUSCH, it
with the is
PUSCH recommended
that the
proportion be
controlled so
that the
number of
non-shared
RBs of AN
format3 and
AN format4
within the
BWP does not
exceed 6.
PUCCH Format3 dynamic preemption function provisioning parameter UME path:

RAN Configuration Management > General Configuration > MO Content > Select NE
>ManagedElement>NRRadioInfrastructure>NRPhysicalCellDU>RBAllocControl>
rbShareSwitch4ANf3f4andPUSCH
Figure 42 AN Format3 And Figure 4: Enabling Dynamic Preemption Of RB
RAN Configuration Management > General Configuration > MO Content> Select NE

>ManagedElement>NRRadioInfrastructure>NRPhysicalCellDU>PhyResourceConfigforBWPUL >PUCCHConfig>
extraANResRBRatio
Figure 43 Confirming The Ratio Of RBs Of Shared AN Format3/4
70 - 108
PUCCH Management
Taking the TNR 100M 5ms single frame structure as an example, configure it according to the current version of the UME system.
The switches of AN format3&4 dynamic preemption RB are set to close, and the function is disabled after cell reset.
Table 40 The Dynamic Preemption in PUCCH Format3 Feature Deactivation
No. Parameter ID Parameter Name Configurati Parameter Path

on Example
1 RBAllocControl.rbShare Switch of sharing RBs of AN close Managed

Switch4ANf3f4andPUSC format3 and AN format4 with Element/NRRadioInfrastructure/NRPhysicalCellDU/RB
H the PUSCH Alloc Control
PUCCH Format3 dynamic preemption function provisioning parameter UME path:

RAN Configuration Management > General Configuration > MO Content > Select NE
>ManagedElement>NRRadioInfrastructure>NRPhysicalCellDU>RBAllocControl>
rbShareSwitch4ANf3f4andPUSCH
Figure 44 AN Format3, 4 Disabling Dynamic Preemption RB
71 - 108
PUCCH Management
5.4.1.5 Test Method
Table 41 PUCCH Format3 Dynamic Preemption Test Method
Test Item PUCCH Format3 dynamic preemption test
Sub-Item N/A
Prerequisites 1. TNR's 2.5ms dual or 5ms single frame structure, with the carrier bandwidth 100M, and the cell is in service.
Test step 1、Format3, 4 Dynamic preemption RB switch is disabled，The uplink and downlink speed tests of the UE reach the
maximum value；
2、Modification：Format3, 4 Dynamic preemption RB switch is enabled，Confirm the RB ratio of the shared AN
format3/4，The uplink and downlink speed tests of the UE reach the maximum value 。
Expected Result Number of available PUSCH PRBs: Enabled > Disable

Number of PRBs occupied by the PUCCH: Enabled < Disabled
The detail result shows in5.4.1.6 Provisioning Observation
Taking the TNR 100M 5ms single frame structure as an example, configure it according to the current version of the UME system，less PRBs
available on the PUCCH after the feature Is enabled.
1、Format3, 4 Dynamic preemption RB switch is disabled，The uplink and downlink speed tests of the UE reach the maximum value，Viewing
KPI（Number of PRBs available by the PUSCH and Number of PRBs occupied by the PUCCH).
Figure 45 AN Format3, 4 Disabling Dynamic Preemption RB
72 - 108
PUCCH Management
2、Format3, 4 Dynamic preemption RB switch is enabled，Confirm the RB ratio of the shared AN format3/4，The uplink and downlink speed
tests of the UE reach the maximum value，Viewing KPI（Number of PRBs available by the PUSCH and Number of PRBs occupied by the
PUCCH）。
Figure 46 AN Format3, 4 Enabling Dynamic Preemption Of RB
3.
Number of available PUSCH PRBs: Enabled > Disable
Number of PRBs occupied by the PUCCH: Enabled < Disabled
The PUCCH Format3 dynamic preemption function takes effect.
6 PUCCH Capacity Adaptation Management

For a heavily loaded cell with a large number of users in the network, if the PUCCH resource allocation is insufficient, the cell KPIs and user
experience will be affected. For a cell with low load, if too many PUCCH resources are configured, the efficiency of spectrum resources will be
affected. Fixed-level resources may be bottlenecked in PUCCH resource allocation when the number of users changes. Therefore, with the
change of the number of users, dynamic adjustment of PUCCH resources is required. The capacity adaptation function balances the system
capacity and resource efficiency to ensure that services such as cell access services can operate properly under high load and system resources
can be used effectively under low load. This feature is applicable to the scenarios where the number of users is not constant and changes
greatly within a certain range. For example, entrances and exits of railway stations, stadiums, and subway stations.
PUCCH capacity adaptation brings the following benefits to network operators:
■ Operation cost reduction and efficiency improvement: The PUCCH capacity adaptation feature provides an effective method for
network operators to optimize network resources, so that the number of users and peak cell traffic can be balanced to improve the
efficiency of spectrum resources.
■ Reduces operation complexity: In scenarios where the number of users changes greatly, the PUCCH capacity adaptation feature can
reduce manual participation and simplify configuration management.
6.1 Principle
73 - 108
PUCCH Management
The NM switch NRPhysicalCellDU.resourceExpansion determines whether to expand resources. If it is "true", it supports resource
expansion，the initial resources are configured through SRResCfg, CSIRptResCfg and ANResCfg; if it is "false", it does not support resource
expansion; and if the resource expansion reaches the upper limit, it will not expand new resources,the resources are configured through
SRResource, CSIReportResource and ANResource.
PUCCH capacity adaptation includes SR capacity adaptation, CSI capacity adaptation, and AN capacity adaptation. Where:
■ SR capacity adaptation and CSI capacity adaptation,refer to 6.1.1 SR/CSI Adaptation principle.
■ AN capacity adaptation refer to 6.1.2 AN Adaptation principle.
6.1.1 SR/CSI Adaptation principle
When the UE accesses the network, allocate available SR/CSI resources in the initial resource pool. When the extension conditions are met, the
corresponding resource expansion will be triggered. After the expansion, the number of resources should be less than the set reduction
minimum value.
When a UE is released, if the available resources reach the scale-in threshold, and no resources are allocated to the RBs to be recycled, the
corresponding RBs are recycled.
SR and CSI resources are expanded independently. The RB positions are arranged in sequence during expansion, and RBs of the forbidden,
shared, and high-interference types are avoided.
The resource period on the extended RB can be set through the PucchAlloc.srPeriod4Expansion and PucchAlloc.csiPeriod4Expansion
parameters.
Figure 47 SR/CSI Resource Expansion in the Non-frequency Hopping Scenario
Figure 48 SR/CSI Resource Expansion in the Frequency Hopping Scenario
Note: The number of existing resources can be calculated through the period, number of RBs, number of symbols, and code channel interval.
6.1.2 AN Adaptation principle
The usage of AN resources is related to scheduling. The scaling of AN resources is determined by comparing the number of users scheduled on
each RB with the preset conditions.
■ If the percentage of the number of scheduled users of each RB to the specified number of users is larger than the specified condition,
the AN resources are extended.

■ If the ratio of the number of scheduled users to the specified number of users of each RB is smaller than the specified condition, AN
74 - 108
PUCCH Management
resources are shrunk.
During AN resource expansion, RBs are arranged in order to avoid forbidden, shared, and high-interference RBs.
Figure 49 AN Resource Expansion in the Non-frequency Hopping Scenario
Figure 50 AN Resource Expansion in the Frequency Hopping Scenario
Note:
PUCCH capacity adaptation brings the following benefits to network operators:
■ Improves operational cost efficiency. PUCCH capacity adaptation provides an effective measure for network operators to optimize
network resources, and allows network operators to use minimum network resources to meet the requirements of more subscribers.
■ Reduces operation complexity: In scenarios where the number of users varies greatly, capacity adaptation can reduce manual
intervention.
When the number of UEs increases, the cell capacity can be increased by expanding the PUCCH resource pools. However, this reduces PUSCH
resources and thus affects the uplink peak traffic of the cell.
This feature is applicable to the scenarios where the number of users changes frequently within a certain range, such as railway stations,
stadiums, and entrances and exits of subway stations.
6.4.1 PUCCH Capacity Adaptation Configuration Provisioning Guidance
75 - 108
PUCCH Management
5GC/EPC 5GC None
BBU V9200 None
CN None.
UE None
FTP server None
1 When this function is enabled, it is recommended that SrsAlloc.srsAdaptAllocSwitch be configured as "Open".
2 When configuring multiple dedicated BWPs, configure NRPhysicalCellDU.pucchResShareSwch as "true".
3 In small-bandwidth (50 M, 40 M, 30 M, 25 M, 20 M) and V3D board small T stations above 3Normal Cell(CP) scenarios, the PUCCH
capacity adaptive function supports a maximum of 400 RRC temporarily.
Before enabling this function, enable the resource adaptation function.
Table 44 Configuration Steps and Parameters of PUCCH Capacity Adaptation
No. Step Related Parameter Verification
1 Switch of resource expansion NRPhysicalCellDU.resourceExpansion None
2 SR resource expansion period PucchAlloc.srPeriod4Expansion None
3 CSI resource expansion period PucchAlloc.csiPeriod4Expansion None
4 PUCCH format for SR transmission SRResCfg.srfmt None
5 Number of PUCCH RBs for SR transmission(RB) SRResCfg.rb4SR None
6 Number of PUCCH symbols for SR transmission(symbol) SRResCfg.sym4SR None
7 Start symbol of the SR PUCCH SRResCfg.startSym4SR None
8 SR transmission period SRResCfg.tranPeriod4SR None
9 Code channel interval SRResCfg.deltaCHfmt None
10 SR transmission period scale SRResCfg.srTrCHNumScale None
11 CQI period multiple coefficient CSIRptResCfg.multiplePeriodCoeff4CQI None
12 RSRP period multiple coefficient CSIRptResCfg.multiplePeriodCoeff4RSRP None
13 PMI period multiple coefficient CSIRptResCfg.multiplePeriodCoeff4PMI None
76 - 108
PUCCH Management
14 PUCCH format for CSI reporting CSIRptResCfg.cSIfmt None
15 Start symbol of the CSI PUCCH CSIRptResCfg.startSym4CSI None
16 Number of PUCCH RBs for CSI reporting(RB) CSIRptResCfg.rbNum4CSI None
17 Number of PUCCH symbols for CSI reporting(symbol) CSIRptResCfg.symNum4PerCSI None
18 CSI reporting period CSIRptResCfg.trPeriod4CSI None
19 Number of RBs in a CSI reporting period CSIRptResCfg.userPeriod4CSI None
20 PUCCH format for AN transmission ANResCfg.anckFmt None
21 Start symbol of the AN PUCCH ANResCfg.startSym4AN None
22 Number of PUCCH RBs for AN transmission(RB) ANResCfg.Rb4AN None
23 Number of PUCCH symbols for AN transmission(symbol) ANResCfg.symNum4PerAN None
24 Code Channel Interval ANResCfg.deltaCHfmt None
25 usageAn ANResCfg.usageAN None
6.4.1.3.2.1 FR1 TDD
path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU
Table 45 Activation of the PUCCH Capacity Adaptation Management Feature

D r Name tion Exa
mple
1 NRPhysical Switch of true Managed The parameter is configured based

on
Figure 51 Activation of the PUCCH Capacity Adaptation Management Feature
77 - 108
PUCCH Management
path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PHYResourceConfigUL/PucchAlloc
Table 46 Activation of Resource Expansion Period Feature
No. Paramete Paramete Configura Parameter Path Configuration Principle

r ID r Name tion Exa
mple
1 PucchAll SR 80 Managed This parameter should be

oc.srPeri resource Element/NRRadioInfrastructure/NRPhysicalCellDU/UL configured based on user
od4Expa expansion physical channel resource configuration/PUCCH experience and UE access capacity.
nsion
period resource allocation parameter If a large number of RRC
connections can be expanded but if
it is required that the SR resources
should occupy a small number of
RBs, set this parameter to a larger
value. To guarantee service
experience of the UEs with capacity
expansion, set this parameter to a
smaller value.
2 PucchAll CSI 320 Managed This parameter should be

oc.csiPeri resource Element/NRRadioInfrastructure/NRPhysicalCellDU/UL configured based on user
nsion
it is required that the CSI resources
smaller value.
Figure 52 Resource Expansion Period of the PUCCH Capacity Adaptation Management Feature
78 - 108
PUCCH Management
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/SRResCfg
Table 47 Activation of the SR Capacity Adaptation Feature

e
1 SRResCfg PUCCH format 1 Managed This

.srfmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool should be
based on the
required SR
PUCCH
format. In
the current
version, this
parameter
can be set to
only format1
in low
frequency
and FR1 FDD
scenarios.
79 - 108
PUCCH Management

transmission RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
number of
available
RBs on the
PUSCH and
the uplink
peak rate to
decrease.
3 SRResCfg Number of 14 Managed This

.sym4SR PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
symbols for configuration/Configuration for PUCCH resource adaptation/SRResCfgPool should be
SR set to the
transmission maximum
number of
available
symbols. If it
is set to 14,
one RB can
bear the
maximum
number of
UEs on the
SR PUCCH of
foramt1.
4 SRResCfg Start symbol 0 Managed The

.startSym of the SR Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
4SR PUCCH configuration/Configuration for PUCCH resource adaptation/SRResCfgPool value
depends on
the available
start symbol.
80 - 108
PUCCH Management

RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
latency to
increase.
6 SRResCfg Code 3 Managed The

determined
based on the
simulation
performance
of the
physical
layer. If this
parameter is
set to a
larger value,
the SR
interference
between
UEs can be
reduced.
However,
the number
of available
SR resources
becomes
smaller.
81 - 108
PUCCH Management
7 SRResCfg SR 5;4;1 Managed To support a

.srTrCHN transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH large
umScale period scale configuration/Configuration for PUCCH resource adaptation/SRResCfgPool number of
RRC
connections,
increase the
scale of the
large-period
SR
resources.
However, if
the scale of
the large-
period SR
resources is
too large, it
may cause
the overall
latency in
the cell to
increase.
Figure 53 Activation of the SR Capacity Adaptation Feature
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/CSIRptResCfg
Table 48 Activation of the CSI Capacity Adaptation Feature
No. Paramete Parameter Configurat Parameter Path Configuration

r ID Name ion Examp Principle
le

82 - 108
PUCCH Management
dCoeff4C coefficient accordance

QI with the
required CQI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
83 - 108
PUCCH Management
period is the
same as the
RSRP
reporting
period. If the
CQI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.

dCoeff4R
SRP
with the
required RSRP
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
84 - 108
PUCCH Management
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
RSRP
reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.

dCoeff4P
MI
with the
required PMI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
85 - 108
PUCCH Management
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
to 1, then, the
PMI reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
PMI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
86 - 108
PUCCH Management
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
4 CSIRptRe PUCCH format 3 Managed This

sCfg.cSIf format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
mt CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool should be
reporting configured
based on the
required CSI
PUCCH
format. For
the current
version, this
parameter can
be set to
format3 or
format4 in low
frequency and
FR1 FDD
scenarios. To
use a certain
format, add a
new record.
Compared
with format 4,
format 3
supports
more bits but
fewer UEs.
5 CSIRptRe Start 0 Managed This

sCfg.start symbol of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
Sym4CSI the CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool set to 0. In the
PUCCH current
version, no
scenario
requires
modifying the
parameter
value.

CSI accordance
reporting with the
actual service
type.

sCfg.sym of PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
Num4Per symbols configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool should be set
CSI
for CSI to the
reporting maximum
number of
available
symbols.
87 - 108
PUCCH Management
8 CSIRptRe CSI 80,160,320 Managed This

configured
based on user
experience
and UE access
capacity. The
larger the
value of an
element is, the
more the
corresponding
UEs are
supported.
The smaller
the value of an
element is, the
fewer the
corresponding
UEs are
supported.
9 CSIRptRe Number 0,3,0 Managed This

sCfg.user of RBs in a Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
Period4C CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool configured
SI
reporting based on the
period number of
RRC -
connection
UEs
supported by
the system.
The larger the
number of
RRC-
connection
UEs is, the
larger the
parameter
value is. The
smaller the
number of
RRC-
connection
UEs is, the
smaller the
parameter
value is.
Figure 54 Activation of the CSI Capacity Adaptation Feature
88 - 108
PUCCH Management
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/ANResCfg
Table 49 Activation of the A/N Capacity Adaptation Feature

mple
1 ANResCfg PUCCH format 1 Managed In common

.anckFmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH scenarios, set
AN configuration/Configuration for PUCCH resource adaptation/AN resource pool this parameter
transmission to format1,
format3, or
format4. In
some special
test scenarios,
set this
parameter to
format0 or
format2.
2 ANResCfg Start symbol sym0 Managed This

.startSym of the AN Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
4AN PUCCH configuration/Configuration for PUCCH resource adaptation/AN resource pool set to 0. In the
current
version, no
scenario
requires
modifying the
parameter
value.

.Rb4AN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
for AN configuration/Configuration for PUCCH resource adaptation/AN resource pool configured in
transmission accordance
with the actual
service type.
89 - 108
PUCCH Management

.symNum PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
4PerAN symbols for configuration/Configuration for PUCCH resource adaptation/AN resource pool should be set
AN to the
number of
available
symbols.
5 ANResCfg Code 3 Managed If serious

mt interval configuration/Configuration for PUCCH resource adaptation/AN resource pool exists between
code channels
in AN PUCCH
format1, the
ratio of
downlink DTX
becomes high.
In this case,
set this
parameter to a
larger value.
6 ANResCfg AN usage normal Managed To support

.usageAN type Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH semi-static
configuration/Configuration for PUCCH resource adaptation/AN resource pool scheduling in
VoNR
scenarios, set
this parameter
to semi-static
scheduling
(sps). To
support
dynamic
codebook in
CA scenarios,
set this
parameter to
CA dynamic
scheduling
(srsTxSwch).
In other
scenarios, it is
recommended
that this
parameter be
set to single-
carrier
dynamic
scheduling
(normal).
Figure 55 Activation of the A/N Capacity Adaptation Feature
90 - 108
PUCCH Management
6.4.1.3.2.2 FR1 FDD
Table 50 Activation of the PUCCH Capacity Adaptation Management Feature

D r Name tion Exa
mple
1 NRPhysical Switch of true Managed The parameter is configured based

on
Figure 56 Activation of the PUCCH Capacity Adaptation Management Feature
91 - 108
PUCCH Management
path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PHYResourceConfigUL/PucchAlloc
Table 51 Activation of Resource Expansion Period Feature
No. Paramete Paramete Configura Parameter Path Configuration Principle

r ID r Name tion Exa
mple
1 PucchAll SR 80 Managed This parameter should be

oc.srPeri resource Element/NRRadioInfrastructure/NRPhysicalCellDU/UL configured based on user
nsion
it is required that the SR resources
smaller value.
2 PucchAll CSI 320 Managed This parameter should be

oc.csiPeri resource Element/NRRadioInfrastructure/NRPhysicalCellDU/UL configured based on user
nsion
it is required that the CSI resources
smaller value.
Figure 57 Resource Expansion Period of the PUCCH Capacity Adaptation Management Feature
92 - 108
PUCCH Management
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/SRResCfg
Table 52 Activation of the SR Capacity Adaptation Feature

e
1 SRResCfg PUCCH format 1 Managed This

.srfmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
SR configuration/Configuration for PUCCH resource adaptation/SRResCfgPool should be
based on the
required SR
PUCCH
format. In
the current
version, this
parameter
can be set to
only format1
in low
frequency
and FR1 FDD
scenarios.
93 - 108
PUCCH Management

transmission RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
number of
available
RBs on the
PUSCH and
the uplink
peak rate to
decrease.
3 SRResCfg Number of 13 Managed This

.sym4SR PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
symbols for configuration/Configuration for PUCCH resource adaptation/SRResCfgPool should be
SR set to the
number of
available
symbols. If it
is set to 14,
one RB can
bear the
maximum
number of
UEs on the
SR PUCCH of
foramt1.
4 SRResCfg Start symbol 0 Managed The

.startSym of the SR Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
4SR PUCCH configuration/Configuration for PUCCH resource adaptation/SRResCfgPool value
depends on
the available
start symbol.
94 - 108
PUCCH Management

RRC
connections,
increase the
parameter
value.
However, if
the
parameter
value is too
large, it may
cause the
latency to
increase.
6 SRResCfg Code 3 Managed The

determined
based on the
simulation
performance
of the
physical
layer. If this
parameter is
set to a
larger value,
the SR
interference
between
UEs can be
reduced.
However,
the number
of available
SR resources
becomes
smaller.
95 - 108
PUCCH Management
7 SRResCfg SR 5;2;1 Managed To support a

.srTrCHN transmission Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH large
umScale period scale configuration/Configuration for PUCCH resource adaptation/SRResCfgPool number of
RRC
connections,
increase the
scale of the
large-period
SR
resources.
However, if
the scale of
the large-
period SR
resources is
too large, it
may cause
the overall
latency in
the cell to
increase.
Figure 58 Activation of the SR Capacity Adaptation Feature
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/CSIRptResCfg
Table 53 Activation of the CSI Capacity Adaptation Feature
No. Paramete Parameter Configurat Parameter Path Configuration

r ID Name ion Examp Principle
le

96 - 108
PUCCH Management
dCoeff4C coefficient accordance

QI with the
required CQI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
97 - 108
PUCCH Management
period is the
same as the
RSRP
reporting
period. If the
CQI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.

dCoeff4R
SRP
with the
required RSRP
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
98 - 108
PUCCH Management
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
set to 1, then,
the PMI
reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
RSRP
reporting
period
calculated
through
configuration
is too large,
the downlink
channel
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.

dCoeff4P
MI
with the
required PMI
reporting
period. The
relation
between the
PMI, CQI, and
RSRP
reporting
periods needs
to be
99 - 108
PUCCH Management
considered in
a unified
manner. By
configuring
the PMI period
multiple
coefficient,
CQI period
multiple
coefficient,
and RSRP
period
multiple
coefficient,
you can
determine the
multiple
relation
between the
PMI reporting
period, CQI
reporting
period, and
RSRP
reporting
period. For
example,
suppose the
PMI period
multiple
coefficient is
set to 2, the
CQI period
multiple
coefficient is
set to 1, and
the RSRP
period
multiple
coefficient is
to 1, then, the
PMI reporting
period is twice
the CQI
reporting
period, and
the CQI
reporting
period is the
same as the
RSRP
reporting
period. If the
PMI reporting
period
calculated
through
configuration
is too large,
the downlink
channel
100 - 108
PUCCH Management
quality
monitoring
effect may be
reduced and
the downlink
traffic may be
affected.
4 CSIRptRe PUCCH format 3 Managed This

sCfg.cSIf format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
mt CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool should be
reporting configured
based on the
required CSI
PUCCH
format. For
the current
version, this
parameter can
be set to
format3 or
format4 in low
frequency and
FR1 FDD
scenarios. To
use a certain
format, add a
new record.
Compared
with format 4,
format 3
supports
more bits but
fewer UEs.
5 CSIRptRe Start 0 Managed This

sCfg.start symbol of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
Sym4CSI the CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool set to 0. In the
PUCCH current
version, no
scenario
requires
modifying the
parameter
value.

CSI accordance
reporting with the
actual service
type.

sCfg.sym of PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
Num4Per symbols configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool should be set
CSI
for CSI to the
reporting maximum
number of
available
symbols.
101 - 108
PUCCH Management
8 CSIRptRe CSI 80,160,320 Managed This

configured
based on user
experience
and UE access
capacity. The
larger the
value of an
element is, the
more the
corresponding
UEs are
supported.
The smaller
the value of an
element is, the
fewer the
corresponding
UEs are
supported.
9 CSIRptRe Number 1,1,0 Managed This

sCfg.user of RBs in a Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
Period4C CSI configuration/Configuration for PUCCH resource adaptation/CSIRptResCfgPool configured
SI
reporting based on the
period number of
RRC -
connection
UEs
supported by
the system.
The larger the
number of
RRC-
connection
UEs is, the
larger the
parameter
value is. The
smaller the
number of
RRC-
connection
UEs is, the
smaller the
parameter
value is.
Figure 59 Activation of the CSI Capacity Adaptation Feature
102 - 108
PUCCH Management
Path:/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCHConfig/PUCCHResCfg/ANResCfg
Table 54 Activation of the A/N Capacity Adaptation Feature

mple
1 ANResCfg PUCCH format 1 Managed In common

.anckFmt format for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH scenarios, set
AN configuration/Configuration for PUCCH resource adaptation/AN resource pool this parameter
transmission to format1,
format3, or
format4. In
some special
test scenarios,
set this
parameter to
format0 or
format2.
2 ANResCfg Start symbol sym0 Managed This

.startSym of the AN Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
4AN PUCCH configuration/Configuration for PUCCH resource adaptation/AN resource pool set to 0. In the
current
version, no
scenario
requires
modifying the
parameter
value.

.Rb4AN PUCCH RBs Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter is
for AN configuration/Configuration for PUCCH resource adaptation/AN resource pool configured in
transmission accordance
with the actual
service type.
103 - 108
PUCCH Management

.symNum PUCCH Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH parameter
4PerAN symbols for configuration/Configuration for PUCCH resource adaptation/AN resource pool should be set
AN to the
number of
available
symbols.
5 ANResCfg Code 3 Managed If serious

mt interval configuration/Configuration for PUCCH resource adaptation/AN resource pool exists between
code channels
in AN PUCCH
format1, the
ratio of
downlink DTX
becomes high.
In this case,
set this
parameter to a
larger value.
6 ANResCfg AN usage normal Managed To support

.usageAN type Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUCCH semi-static
configuration/Configuration for PUCCH resource adaptation/AN resource pool scheduling in
VoNR
scenarios, set
this parameter
to semi-static
scheduling
(sps). To
support
dynamic
codebook in
CA scenarios,
set this
parameter to
CA dynamic
scheduling
(srsTxSwch).
In other
scenarios, it is
recommended
that this
parameter be
set to single-
carrier
dynamic
scheduling
(normal).
Figure 60 Activation of the A/N Capacity Adaptation Feature
104 - 108
PUCCH Management
6.4.1.3.2.3 FR2 TDD
FR2 does not support.
6.4.1.4.1 FR1 TDD
Table 55 Deactivation of the PUCCH Capacity Adaptation Feature
No. Parameter ID Parameter Name Configuration Exa Parameter Path

mple
1 NRPhysicalCellDU.resourceEx Switch of resource false Managed

pansion expansion Element/NRRadioInfrastructure/NRPhysicalCellDU
Figure 61 Deactivation of the PUCCH Capacity Adaptation Feature
105 - 108
PUCCH Management
6.4.1.4.2 FR1 FDD
Table 56 Deactivation of the PUCCH Capacity Adaptation Feature
No. Parameter ID Parameter Name Configuration Exa Parameter Path

mple
1 NRPhysicalCellDU.resourceEx Switch of resource false Managed

pansion expansion Element/NRRadioInfrastructure/NRPhysicalCellDU
Figure 62 Deactivation of the PUCCH Capacity Adaptation Feature
106 - 108
PUCCH Management
6.4.1.4.3 FR2 TDD
FR2 not supported.
6.4.1.5 Test Method
Table 57 Test Method
Test item PUCCH capacity self-adaptive test under 2.5 ms frame structure
Subitem N/A
Prerequisite 1 The gNodeB is operating properly.

2 Cell 1 under the gNodeB is in normal status.
3 Multiple UEs can be connected.
Steps 1 Configure relevant parameters by referring to 4.4.1.3 Feature Activation.

2 Make UEs access the cell (the number of UEs should be greater than that defined in the resource pool expansion
condition).
3 Observe the startingPRB parameter in the RRC Reconfiguration message of each UE.
Expected When the number of resources is close to or exceeds the expansion or contraction threshold, the startingPRB values in the
result PUCCH resources of the UEs are different.
Verify that the cell is operating properly and the UE can successfully access the network.
Verify that the PUCCH configuration is sent to the UE through an RRC reconfiguration message. The location of the log on the UME is as follows
: Maintenance Surveillance -> Signaling Trace Analytics ->Cell Trace -> RRCReconfiguration. Use the keyword pucch_Config for searching.
107 - 108
PUCCH Management
Expand the RRCReconfiguration message and use the keyword pucch_Config for searching. View the startingPRB value, see the following
figure.
7 Related Counters, KPIs, and Alarms
7.1 Related Counters
This feature has no related counter.
7.2 Related KPIs
This feature has no related KPI.
7.3 Related Alarms
This feature has no related alarm.
8 Abbreviations
For the acronyms, refer to the abbreviations.
9 References
1. 3GPP TS 38.211, “NR; Physical channels and modulation”
2. 3GPP TS 38.212, “NR; Multiplexing and channel coding”
3. 3GPP TS 38.213, “NR; Physical layer procedures for control”
4. 3GPP TS 38.331, “NR; Radio Resource Control (RRC); Protocol specification”
5. 3GPP TS 38.214, “NR; Physical layer procedures for data”
108 - 108

PUCCH Management (NR22.2) 1112864

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PUCCH Management (NR22.2) 1112864

Uploaded by

Copyright:

Available Formats

PUCCH Management

Product Version: NR22.2

Copyright ©2020 ZTE CORPORATION.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

The ultimate right to interpret this product resides in ZTE CORPORATION.

1 About This Document

1.1 Personal Data Security Statement

Change Type Change Date Description Parameter Change

2.1 Covered Features

The following table lists the features covered in this document.

Table 1 Covered Feature List

2.2 Correlation with Other Features

Table 2 Correlation with Other Features

ZNR-RB-0050 Channel Management None None None

2.3 Terms and Definitions

Table 3 Terms and Definitions

Term Full Name Definition

ACK ACKnowledgment Indicates that downlink or uplink data is received correctly.

HARQ Hybrid Automatic Data requested to be resent automatically in hybrid mode.

NACK Negative Indicates that downlink or uplink data is received incorrectly.

PBCH Physical Physical-layer broadcast channel, which carries the BCH.

RI Rank Indicator The flow number of PDSCH that can be transmitted.

TA Timing Advance Result of time offset measurement

2.4 Feature Difference Descriptions

2.4.1 Difference Between FR1 FDD and FR1 TDD

Table 4 Difference Between FR1 FDD and FR1 TDD

Feature Difference Description Refer to

2.4.2 Difference Between NSA and SA Networks

Table 5 Difference Between NSA and SA Networks

Feature Difference Description Refer to

2.4.3 Difference Between FR1 and FR2

Table 6 Difference Between FR1 and FR2

Feature Difference Description Refer to

Long PUCCH Support FR1 only. 4.1 Principle

Short PUCCH Support FR2 only. 4.1 Principle

PUCCH blanking Support FR1 only. 4.1 Principle

PUCCH Capacity Adaptation Management Support FR1 only. 6.1 Principle

4 PUCCH Basic Function

■ Scheduling Request (SR): requests UL-SCH resources from the gNodeB.

gNodeB in downlink scheduling.

Table 7 Formats Supported by the PUCCH

Format Number of OFDM Symbols Number of Bits

Table 8 Information Supported by the PUCCH in Different Formats

Format 0 Format 1 Format 2 Format 3 Format 4

Independent SR Independent SR Independent SR Independent CSI Independent CSI

SR+1-bit AN SR+1-bit AN SR+CSI SR+CSI

Figure 1 Resources in Format 1 When Intra-Slot Frequency Hopping Is Disabled

Figure 2 Resources in Format 1 When Intra-Slot Frequency Hopping Is Enabled

Figure 3 Resources in Format 3 When Intra-Slot Frequency Hopping Is Disabled

Figure 4 Resources in Format 3 When Intra-Slot Frequency Hopping Is Enabled

Figure 5 Resources in Format 0 When Intra-Slot Frequency Hopping Is Disabled

When PUCCHResCfg.freqHopping is enabled, its time-frequency resources are shown in Figure 6 .

Figure 6 Resources in Format 0 When Intra-Slot Frequency Hopping Is Enabled

Figure 7 Resources in Format 2 When Intra-Slot Frequency Hopping Is Disabled

When PUCCHResCfg.freqHopping is enabled, its time-frequency resources are shown in Figure 7 .

Figure 8 Resources in Format 2 When Intra-Slot Frequency Hopping Is Disabled

4.2 Network Analysis

4.2.1 Benefit Analysis

demodulation performance can be higher.

4.2.2 Impact Analysis

4.3 Application Scenarios

This feature is applicable to FR1/FR2 TDD and FR1 FDD systems.

4.4 Provisioning Guidance