Channel Management (5G RAN3.1 - Draft A) PDF

5G RAN
Channel Management Feature

Parameter Description
Issue Draft A
Date 2020-01-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

(2020-01-20)
5G RAN
Channel Management Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN3.1 Draft A (2020-01-20)...................................................................................................................................... 1
2 About This Document.............................................................................................................5

2.1 General Statements................................................................................................................................................................ 5
2.2 Features in This Document.................................................................................................................................................. 5
2.3 Differences Between NR FDD and NR TDD................................................................................................................... 6
2.4 Differences Between NSA and SA..................................................................................................................................... 7
2.5 Differences Between High Frequency Bands and Low Frequency Bands............................................................ 8
3 Overview................................................................................................................................. 11
4 PBCH Channel Management.............................................................................................. 12
4.1 Principles.................................................................................................................................................................................. 12
4.2 Network Analysis.................................................................................................................................................................. 18
4.2.1 Benefits................................................................................................................................................................................. 18
4.2.2 Impacts.................................................................................................................................................................................. 18
4.3 Requirements......................................................................................................................................................................... 19
4.3.1 Licenses................................................................................................................................................................................. 19
4.3.2 Software................................................................................................................................................................................19
4.3.3 Hardware.............................................................................................................................................................................. 19
4.3.4 Others.................................................................................................................................................................................... 19
4.4 Operation and Maintenance............................................................................................................................................. 19
4.4.1 Data Configuration........................................................................................................................................................... 19
4.4.1.1 Data Preparation............................................................................................................................................................ 20
4.4.1.2 Using MML Commands............................................................................................................................................... 20
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 20
4.4.2 Activation Verification..................................................................................................................................................... 20
4.4.3 Network Monitoring......................................................................................................................................................... 20
5 PDCCH Channel Management........................................................................................... 21

5.1 Principles.................................................................................................................................................................................. 21
5.2.1 Benefits................................................................................................................................................................................. 24
5.2.2 Impacts.................................................................................................................................................................................. 24
5.3 Requirements......................................................................................................................................................................... 26
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2020-01-20)
5G RAN
5.3.1 Licenses................................................................................................................................................................................. 26
5.3.2 Software................................................................................................................................................................................26
5.3.3 Hardware.............................................................................................................................................................................. 27
5.3.4 Others.................................................................................................................................................................................... 27
6 PUCCH Channel Management........................................................................................... 30

6.1 Principles.................................................................................................................................................................................. 30
6.2.1 Benefits................................................................................................................................................................................. 36
6.2.2 Impacts.................................................................................................................................................................................. 36
6.3 Requirements......................................................................................................................................................................... 39
6.3.1 Licenses................................................................................................................................................................................. 39
6.3.2 Software................................................................................................................................................................................40
6.3.3 Hardware.............................................................................................................................................................................. 41
6.3.4 Others.................................................................................................................................................................................... 41
7 PRACH Channel Management........................................................................................... 48

7.1 Principles.................................................................................................................................................................................. 48
7.1.1 RA Preamble........................................................................................................................................................................ 48
7.1.1.1 Overview........................................................................................................................................................................... 48
7.1.1.2 Preamble Sequence Generation................................................................................................................................ 50
7.1.1.3 Preamble Sequence Grouping................................................................................................................................... 50
7.1.2 Time-Frequency Resources for RA............................................................................................................................... 52
7.1.3 Increasing the PRACH Preamble Detection Threshold......................................................................................... 54
7.1.4 PRACH Root Sequence Conflict Detection and Self-optimization....................................................................55
7.1.5 Optimization of Non-Contention-based RA Beyond Cell Radius......................................................................56
7.2.1 Benefits................................................................................................................................................................................. 56
7.2.2 Impacts.................................................................................................................................................................................. 57
7.3 Requirements......................................................................................................................................................................... 57
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2020-01-20)
5G RAN
7.3.1 Licenses................................................................................................................................................................................. 57
7.3.2 Software................................................................................................................................................................................57
7.3.3 Hardware.............................................................................................................................................................................. 58
7.3.4 Others.................................................................................................................................................................................... 58
8 CSI-RS Resource Management........................................................................................... 61

8.1 Principles.................................................................................................................................................................................. 61
8.2.1 Benefits................................................................................................................................................................................. 63
8.2.2 Impacts.................................................................................................................................................................................. 63
8.3 Requirements......................................................................................................................................................................... 64
8.3.1 Licenses................................................................................................................................................................................. 64
8.3.2 Software................................................................................................................................................................................64
8.3.3 Hardware.............................................................................................................................................................................. 65
8.3.4 Others.................................................................................................................................................................................... 65
9 SRS Resource Management................................................................................................ 68

9.1 Principles.................................................................................................................................................................................. 68
9.1.1 Overview............................................................................................................................................................................... 68
9.1.2 Cell-specific SRS................................................................................................................................................................. 70
9.1.3 UE-specific SRS................................................................................................................................................................... 70
9.1.3.1 UE-specific SRS Slot.......................................................................................................................................................70
9.1.3.2 UE-specific SRS Bandwidth......................................................................................................................................... 70
9.1.4 SRS Multiplexing................................................................................................................................................................ 71
9.1.5 SRS Frequency Hopping.................................................................................................................................................. 72
9.2.1 Benefits................................................................................................................................................................................. 72
9.2.2 Impacts.................................................................................................................................................................................. 73
9.3 Requirements......................................................................................................................................................................... 75
9.3.1 Licenses................................................................................................................................................................................. 75
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

(2020-01-20)
5G RAN
9.3.2 Software................................................................................................................................................................................75
9.3.3 Hardware.............................................................................................................................................................................. 75
9.3.4 Others.................................................................................................................................................................................... 76
10 Parameters............................................................................................................................79
11 Counters................................................................................................................................ 80
12 Glossary................................................................................................................................. 81
13 Reference Documents........................................................................................................ 82
Issue Draft A Copyright © Huawei Technologies Co., Ltd. v

(2020-01-20)
5G RAN
Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 5G RAN3.1 Draft A (2020-01-20)

This issue introduces the following changes to 5G RAN2.1 (2019-06-06).
Technical Changes
Change Description Parameter Change Base Station Model
Added support for three Added the value 3SYM(3 ● 3900 and 5900
physical downlink control Symbols) to the series base stations
channel (PDCCH) NRDUCellPdcch.Occupied ● DBS3900 LampSite
symbols by NR FDD. For SymbolNum parameter. and DBS5900
details, see 5 PDCCH LampSite
Channel Management.
Added support for Added the ● 3900 and 5900

PDCCH symbol number UE_PDCCH_SYM_NUM_AD series base stations
adaptation. For details, APT_SW option to the ● DBS3900 LampSite
see 5 PDCCH Channel NRDUCellPdcch.PdcchAlg and DBS5900
Management. oExtSwitch parameter. LampSite
Added PDCCH initial Added the ● 3900 and 5900

aggregation level NRDUCellPdcch.PdcchAlg series base stations
selection optimization. oEnhSwitch parameter. ● DBS3900 LampSite
For details, see 5 PDCCH and DBS5900
Channel Management. LampSite
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2020-01-20)
5G RAN

PDCCH uplink-to- NRDUCellPdcch.PdcchAlg series base stations
downlink control channel oSwitch parameter. ● DBS3900 LampSite
element (CCE) ratio and DBS5900
adaptation. For details, LampSite
see 5 PDCCH Channel
Management.
Added support for Added the 3900 and 5900 series

symbol adaptation in NRDUCellPucch.PucchAlg base stations
short physical uplink oSwitch parameter.
control channel (PUCCH)
formats in high frequency
bands. For details, see 6
PUCCH Channel
Management.

PUCCH time-frequency NRDUCellPucch.Structure series base stations
format configuration in Type parameter. ● DBS3900 LampSite
low frequency bands. For and DBS5900
details, see 6 PUCCH LampSite
Channel Management.
Added support for Added the following ● 3900 and 5900

PUCCH format 4. For parameters: series base stations
details, see 6 PUCCH ● NRDUCellPucch.Forma ● DBS3900 LampSite
Channel Management. t4RbNum and DBS5900
● NRDUCellPucch.Forma LampSite
t4CsiDedicatedRbNum
Added support for RB Added the ● 3900 and 5900
adaptation in long PUCCH_RBRES_ADAPTIVE series base stations
PUCCH formats. For _SWITCH option to the ● DBS3900 LampSite
details, see 6 PUCCH NRDUCellPucch.PucchAlg and DBS5900
Channel Management. oSwitch parameter. LampSite

scheduling request (SR) NRDUCellPucch.SrResour series base stations
period adaptation. For eAlgoSwitch parameter. ● DBS3900 LampSite
details, see 6 PUCCH and DBS5900
Channel Management. LampSite

channel state information NRDUCellPucch.CsiResour series base stations
(CSI) reporting period eAlgoSwitch parameter. ● DBS3900 LampSite
adaptation. For details, and DBS5900
see 6 PUCCH Channel LampSite
Management.

(2020-01-20)
5G RAN
Modified the CSI ● Added the ● 3900 and 5900

reference signal (CSI-RS) NRDUCellCsirs.CsirsCel series base stations
period configuration lResourceNum ● DBS3900 LampSite
scheme. For details, see 8 parameter. and DBS5900
CSI-RS Resource ● Modified the default LampSite
Management. value of the
NRDUCellCsirs.CsiPerio
d parameter.
● Added the
NRDUCellCsirs.CsiAlgo
Switch parameter to
the disuse list.

sounding reference signal NRDUCellSrs.SrsAlgoSwit series base stations
(SRS) period adaptation ch parameter. ● DBS3900 LampSite
in low frequency bands. and DBS5900
For details, see 9 SRS LampSite
Resource Management.
Modified the default None ● 3900 and 5900

physical random access series base stations
channel (PRACH) ● DBS3900 LampSite
configuration index for and DBS5900
slot assignment 4:1. For LampSite
details, see 7.1.2 Time-
Frequency Resources for
RA.
Optimized non- Added the ● 3900 and 5900

contention-based random NRDUCellPrach.RachAlgo series base stations
access beyond cell radius. OptSwitch parameter. ● DBS3900 LampSite
For details, see 7.1.5 and DBS5900
Optimization of Non- LampSite
Contention-based RA
Beyond Cell Radius.
Added support for 120 None 3900 and 5900 series

kHz subcarrier spacing base stations
(SCS) used by the PRACH
in high frequency bands.
For details, see 7.1.1.1
Overview.

(2020-01-20)
5G RAN
Added support for PRACH None ● 3900 and 5900

root sequence conflict series base stations
detection and self- ● DBS3900 LampSite
optimization. For details, and DBS5900
see 7.1.4 PRACH Root LampSite
Sequence Conflict
Detection and Self-
optimization.
Added support fot an Added the ● 3900 and 5900

increased PRACH NRDUCellPrach.PrachThld series base stations
preamble detection IncreaseRate parameter. ● DBS3900 LampSite
threshold. For details, see and DBS5900
7.1.3 Increasing the LampSite
PRACH Preamble
Detection Threshold.
Changed the name of None ● 3900 and 5900

U2020 to MAE-Access series base stations
and the name of CME to ● DBS3900 LampSite
MAE-Deployment. and DBS5900
LampSite
Editorial Changes
● Added descriptions of physical broadcast channel (PBCH) channel
management. For details, see 4 PBCH Channel Management.
● Added descriptions of PRACH channel management. For details, see 7 PRACH
Channel Management. Deleted descriptions of the RA process. For details
about the RA process, see 5G Networking and Signaling.
● Deleted the descriptions of uplink timing. For details about uplink timing, see
5G Networking and Signaling.
● Reorganized the document and optimized descriptions.

(2020-01-20)
5G RAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
2.2 Features in This Document

This document describes the following features.

(2020-01-20)
5G RAN
Feature Feature Name Section

ID
FBFD-01 Channel Management 4 PBCH Channel

0009 Management
5 PDCCH Channel
Management
6 PUCCH Channel
Management
7 PRACH Channel
Management
8 CSI-RS Resource
Management
9 SRS Resource
Management
2.3 Differences Between NR FDD and NR TDD

Function Name Difference Section
Physical broadcast This function is supported by both 4 PBCH Channel

channel (PBCH) NR FDD and NR TDD, with the Management
channel following differences:
management The supported time-domain patterns
vary between NR FDD and NR TDD.
Physical downlink This function is supported by both 5 PDCCH Channel

control channel NR FDD and NR TDD, with the Management
(PDCCH) channel following differences:
management NR TDD allows for one or two
PDCCH symbols, whereas NR FDD
allows for one, two, or three PDCCH
symbols.
Physical uplink None 6 PUCCH Channel

control channel Management
(PUCCH) channel
management

(2020-01-20)
5G RAN
Physical random This function is supported by both 7 PRACH Channel

access channel NR FDD and NR TDD, with the Management
(PRACH) channel following differences:
management The supported random access (RA)
preamble formats, PRACH
configuration indexes, and number
of physical resource blocks (PRBs) for
the PRACH are different between NR
TDD and NR FDD. For details, see
7.1.1.1 Overview and 7.1.2 Time-
Frequency Resources for RA.
Channel state This function is supported by both 8 CSI-RS Resource

information- NR FDD and NR TDD, with the Management
reference signal following differences:
(CSI-RS) resource Only NR TDD, not NR FDD, allows
management for CSI-RS for beam measurement
(CSI-RS for BM).
Sounding reference This function is supported by both 9 SRS Resource

signal (SRS) NR FDD and NR TDD, with the Management
resource following differences:
management NR FDD only supports SRS resources
with the usage of codebook, whereas
NR TDD supports SRS resources with
the usage of codebook and
antennaSwitching.
SRS is transmitted in uplink-only
slots in NR FDD and in self-
contained slots in NR TDD.
NR FDD only involves low frequency bands, and therefore this section describes only the
differences between NR FDD and low-frequency NR TDD. It does not involve high frequency
band scenarios.
2.4 Differences Between NSA and SA

PBCH channel None 4 PBCH Channel

management Management
PDCCH channel None 5 PDCCH Channel


(2020-01-20)
5G RAN
PUCCH channel None 6 PUCCH Channel

PRACH channel None 7 PRACH Channel

CSI-RS resource None 8 CSI-RS Resource

SRS resource None 9 SRS Resource

2.5 Differences Between High Frequency Bands and

Low Frequency Bands
In this document, low frequency bands refer to those belonging to FR1 (410–7125
MHz), and high frequency bands refer to those belonging to FR2 (24250–52600
MHz). For details about FR1 and FR2, see section 5.1 "General" in 3GPP TS 38.104
V15.5.0.
PBCH channel This function is supported in both 4 PBCH Channel

management high and low frequency bands, with Management
the following differences:
Both SA networking and NSA
networking are supported in low
frequency bands, and only NSA
networking is supported in high
frequency bands.
PDCCH channel This function is supported in both 5 PDCCH Channel

frequency bands.

(2020-01-20)
5G RAN
PUCCH channel This function is supported in both 6 PUCCH Channel

frequency bands.
Cell-specific PUCCH time-frequency
formats include short formats and
long formats. Both short formats and
long formats are supported in low
frequency bands, whereas only short
formats are supported in high
frequency bands.
The short PUCCH supports symbol
adaptation only in high frequency
bands. The long PUCCH supports
symbol adaptation only in low
frequency bands.
CSI reporting period adaptation is
supported in low frequency bands
but not in high frequency bands.
PRACH channel This function is supported in both 7 PRACH Channel

frequency bands.
RA preamble formats, PRACH
configuration indexes, and the
number of PRBs for the PRACH are
different in high and low frequency
bands.

(2020-01-20)
5G RAN
CSI-RS resource This function is supported in both 8 CSI-RS Resource

frequency bands.
Periodic CSI-RS for CM and aperiodic
CSI-RS for CM are supported in low
frequency bands, whereas aperiodic
CSI-RS for CM is used in high
frequency bands.
SRS resource This function is supported in both 9 SRS Resource

frequency bands.
Periodic SRS is used in low frequency
bands, whereas aperiodic SRS is used
in high frequency bands.
SRS period adaptation applies only
to periodic SRS and only in low
frequency bands.

(2020-01-20)
5G RAN
Description 3 Overview
3 Overview
Channel resource management maximizes data volume by offering correct

signaling resource configuration, which minimizes signaling resource consumption
and ensures signaling demodulation performance. In an NR system, resource
management is performed for each physical channel, as described in Table 3-1.
Table 3-1 Resource management for channels

Channel Resource Management
Downlink PBCH 4 PBCH Channel

physical Management
channel
PDCCH 5 PDCCH Channel
Management
Physical downlink shared channel For details, see

(PDSCH) Scheduling.
Uplink PUCCH 6 PUCCH Channel
physical Management
channel
PRACH 7 PRACH Channel
Management
Physical uplink shared channel (PUSCH) For details, see

Scheduling.
In addition to the channel resource management outlined in the preceding table,

this document also presents CSI-RS (downlink physical signal) and SRS (uplink
physical signal) resource management. For more information, see 8 CSI-RS
Resource Management and 9 SRS Resource Management.
For more information on physical channels and physical signals, see 3GPP TS
38.211 "NR; Physical channels and modulation."
For details of power configurations of each channel, see Power Control.

(2020-01-20)
5G RAN
Description 4 PBCH Channel Management
4 PBCH Channel Management
4.1 Principles
The PBCH broadcasts the system configurations of a cell.
Position of the PBCH

On an NR network, an SSB (involved in beam sweeping) carries the PBCH, primary
synchronization signal (PSS), and secondary synchronization signal (SSS). An SSB
occupies four consecutive symbols in the time domain, and spreads over 20
resource blocks (RBs) in the frequency domain. Figure 4-1 shows an example SSB,
in which the PSS and SSS occupy symbols 0 and 2 of the SSB, respectively, and the
PBCH occupies symbols 1 and 3 and some resource elements (REs) of symbol 2.
The master information block (MIB), carried in an exclusive RRC message, is
transmitted over the transport channel BCH and then mapped to the REs of the
PBCH. The BCH has a predefined transport format, which enables a UE to receive
the MIB over the BCH to obtain information necessary to access the network
without the need to obtain other information from the network.

(2020-01-20)
5G RAN
Figure 4-1 Example SSB
Table 4-1 OFDM symbols and subcarriers within an SSB for signals and the
channel
Channel or OFDM Symbol Subcarrier Number
Signal Number
PSS 0 56, 57, ..., 182
SSS 2 56, 57, ..., 182
Set to 0 0 0, 1, ..., 55, 183, 184, ..., 239
2 48, 49, ..., 55, 183, 184, ..., 191

(2020-01-20)
5G RAN
Channel or OFDM Symbol Subcarrier Number

Signal Number
PBCH 1, 3 0, 1, ..., 239
2 0, 1, ..., 47
192, 193, ..., 239
Demodulatio 1, 3 0+v, 4+v, 8+v, ..., 236+v

n reference
signal 2 0+v, 4+v, 8+v, ..., 44+v
(DMRS) for 192+v, 196+v, ..., 236+v
the PBCH
Note: "v" indicates the value returned by cell PCI mod 4. For more information,
see section 7.4.3.1 "Time-frequency structure of an SS/PBCH block" in 3GPP TS
38.211 (Release 15).
● Frequency-domain position
NR allows for flexible configurations of the frequency-domain position of an
SSB. The NRDUCell.SsbFreqPos parameter specifies the SSB's frequency-
domain position in a cell, and the NRDUCell.SsbDescMethod parameter
specifies the description method of the SSB's frequency-domain position. For
details, see Cell Management.
● Time-domain pattern
NR introduces the following SSB patterns in the time domain: case A, case B,
case C, case D, and case E, which suit different subcarrier spacing (SCS) values
and frequency bands. The maximum number of SSBs and the position of the
start symbol vary among the patterns, as shown in Figure 4-2. For details
about the SCS values supported in the current version, see Cell Management.

(2020-01-20)
5G RAN
Figure 4-2 Time-domain SSB pattern
Table 4-2 lists the specifications-defined maximum number of SSBs in

different frequency bands.
Table 4-2 Maximum number of SSBs in different frequency bands

Frequency Band (F) Maximum Number of SSBs
F ≤ 3 GHz FDD: 4
TDD (F ≤ 2.4 GHz): 4
TDD (F > 2.4 GHz): 8
3 GHz < F ≤ 6 GHz 8
F > 6 GHz 64
For more information, see section 4.1 "Cell Search" in 3GPP TS 38.213
(Release 15).
PBCH and SSB Beams

● Number of SSB beams
Each SSB has a unique number, known as an SSB index. In low frequency
bands, the index is directly obtained from the PBCH DMRS. In high frequency
bands, the least and the most significant three bits of the index are obtained
from the PBCH DMRS and MIB, respectively.
The actual number of SSB beams (each corresponding to an SSB index)
transmitted in a cell depends on configurations such as slot assignment and

(2020-01-20)
5G RAN
scenario-specific beam configurations. The number must be less than or equal

to the maximum number of SSBs defined in specifications. SIB1 or RRC
signaling can indicate which SSBs are not transmitted and the PDSCH can be
transmitted in the corresponding vacant positions. For more information on
slot assignment, see Standards Compliance. For more information on
scenario-specific beams, see Beam Management in low frequency bands and
mmWave Beam Management in high frequency bands.
● SSB beam sweeping period
An 80 ms period of SSB transmission is applied. Within each 80 ms period, the
gNodeB repeats SSB beam sweeping over the air interface in a specified case
(SSB pattern). The SSB beam sweeping period can be specified by the
NRDUCell.SsbPeriod parameter. The default SSB beam sweeping period is 20
ms, allowing for four repetitions of SSB beam sweeping within 80 ms. Each
round of beam sweeping is completed within 5 ms.
Figure 4-3 and Figure 4-4 show examples of SSB time sequence diagrams.
According to 3GPP TS 38.213 (Release 15), UEs expect the gNodeB to perform SSB
beam sweeping with a period of 20 ms during initial cell selection. If the actual SSB
beam sweeping period is longer than 20 ms, the UE access duration may increase,
depending on SSB beam detection policies used by UEs.

(2020-01-20)
5G RAN
Figure 4-3 Example SSB time sequence diagram (case A for 2.1 GHz as an
example)

(2020-01-20)
5G RAN
Figure 4-4 Example SSB time sequence diagram (case C for 3.5 GHz as an
example)
4.2 Network Analysis
4.2.1 Benefits
PBCH channel management enables PBCH resources to be properly used to
improve network performance.
4.2.2 Impacts
None

(2020-01-20)
5G RAN
4.3 Requirements
4.3.1 Licenses
This function is a basic function and is not under license control.
4.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models

● 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
Boards
All NR-capable main control boards and baseband processing units support this
function. To learn which main control boards and baseband processing units are
NR-capable, see the related BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR-capable RF modules support this function. For details about NR-capable RF
modules, see technical specifications of the related RF modules in 3900 & 5900
Series Base Station Product Documentation.
4.3.4 Others
None
4.4 Operation and Maintenance
4.4.1 Data Configuration

(2020-01-20)
5G RAN
4.4.1.1 Data Preparation

This function is a basic function and takes effect by default. Activation is not
required. Table 4-3 describes the parameters used for function optimization.
Table 4-3 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name
SSB Period NRDUCell.SsbPeriod Retain the default value.

A shorter SSB beam sweeping
period results in more
overheads. An SSB beam
sweeping period longer than
20 ms increases access delay.
4.4.1.2 Using MML Commands
Activation Command Examples

required.
Optimization Command Examples

//Setting the SSB period
MOD NRDUCELL: NrDuCellId=0, SsbPeriod=MS20;
Deactivation Command Examples

N/A
4.4.1.3 Using the MAE-Deployment

For detailed operations, see MAE-Deployment-based Feature Configuration.
4.4.2 Activation Verification

This function is a basic function and takes effect by default. Activation verification
is not required.
4.4.3 Network Monitoring

This function is a basic function that ensures basic service performance.
Monitoring is not required.

(2020-01-20)
5G RAN
Description 5 PDCCH Channel Management
5 PDCCH Channel Management
5.1 Principles
Overview
The PDCCH carries downlink control information (DCI), which can be SRS DCI or
CSI-RS DCI. DCI carries the following information:
● Downlink grants
These include information such as the PDSCH resource indication, modulation
and coding scheme (MCS), and HARQ process. DCI formats 1_0 and 1_1 are
supported.
● Uplink grants
These include information such as the PUSCH resource indication and MCS.
DCI formats 0_0 and 0_1 are supported.
● Transmit power control (TPC) commands
These include the TPC commands for the PUSCH for a group of UEs,
supplementing the TPC commands for the PUSCH and PUCCH in uplink
grants.
For more information on DCI formats, see section 7.3 "Downlink control information"
in 3GPP TS 38.212 (Release 15).
Position of the PDCCH

Each slot is 14 symbols long (numbered 0 to 13). In accordance with NR
specifications, the PDCCH of a cell occupies the first one to three symbols of a
slot, as shown in Figure 5-1, where each cell in the grid represents an RE. In the
current version, NR TDD supports one or two symbols. NR FDD supports one, two,
or three symbols.

(2020-01-20)
5G RAN
Figure 5-1 Position of the PDCCH
The number of symbols occupied by the PDCCH can be statically or dynamically

configured.
● Static configuration: The NRDUCellPdcch.OccupiedSymbolNum parameter
specifies the number of occupied symbols.
● Dynamic configuration: Select the UE_PDCCH_SYM_NUM_ADAPT_SW option
of the NRDUCellPdcch.PdcchAlgoExtSwitch parameter to enable this
function. After this function is enabled, the setting of the
NRDUCellPdcch.OccupiedSymbolNum parameter does not take effect.
Instead, the number of symbols occupied by the PDCCH is dynamically
adjusted based on required control channel elements (CCEs) and the new
number of symbols is delivered to all UEs through an RRC reconfiguration
message.
– When the PDCCH requires a few CCEs, the number of symbols occupied
by the PDCCH is decreased and idle time-frequency resources are
allocated to the PDSCH.
– When the PDCCH requires many CCEs, the number of symbols occupied
by the PDCCH is increased until the number reaches the maximum value
allowed in static configuration.
PDCCH Uplink-to-Downlink CCE Ratio

For a slot transmitting DCI for uplink and downlink scheduling, the percentage of
available uplink CCEs can be statically or dynamically configured.
● Static configuration through the NRDUCellPdcch.UlMaxCcePct parameter
– A larger value of this parameter results in a higher proportion of
available uplink CCEs and a lower proportion of available downlink CCEs,
decreasing the chances of downlink scheduling.
– A smaller value of this parameter results in a lower proportion of
available uplink CCEs and a higher proportion of available downlink CCEs,
decreasing the chances of uplink scheduling.
● Dynamic configuration: Select the UL_DL_CCE_RATIO_ADAPT_SW option of
the NRDUCellPdcch.PdcchAlgoSwitch parameter to enable this function.

(2020-01-20)
5G RAN
After this function is enabled, the setting of the

NRDUCellPdcch.UlMaxCcePct parameter does not take effect. The ratio of
available uplink CCEs to available downlink CCEs is dynamically adjusted
based on factors such as required uplink and downlink CCEs and CCE resource
usage. Dynamic configuration is enabled by default.
In NR TDD, the dynamically configured ratio takes effect in each slot
transmitting DCI for both uplink and downlink scheduling.
NR FDD networks have a relative small number of CCEs. To ensure coverage,
this function only guarantee that the average ratio can reach the dynamically
configured ratio. The dynamically configured ratio does not directly take
effect in each slot.
A CPE performs blind detection of a maximum 96 PDCCH RBs in low frequency bands. A
CPE performs blind detection of a maximum 48 PDCCH RBs in high frequency bands. For
CPE users, the ratio only takes effect within the CPE's blind detection capability.
PDCCH Aggregation Level

A CCE is the smallest resource unit for PDCCH transmission. One CCE contains six
resource element groups (REGs) and each REG corresponds to a single RB.
Depending on the bit rate, the gNodeB allocates 1, 2, 4, 8, or 16 CCEs for the
PDCCH. The number of CCEs allocated to the PDCCH corresponds to aggregation
level 1, 2, 4, 8, or 16 stipulated in specifications. Aggregation level 1, which is not
supported in the current version, indicates that the PDCCH occupies one CCE,
while aggregation level 2 indicates that the PDCCH occupies two CCEs. The same
rules apply to other aggregation levels.
● PDCCH aggregation level 16 delivers the best demodulation performance but

the lowest bit rate.
Applying PDCCH aggregation level 16 to all UEs in a cell is a waste of PDCCH
CCEs, as cell center users (CCUs) do not require such a level.
● PDCCH aggregation level 1 delivers the highest bit rate but the worst
demodulation performance.
If PDCCH aggregation level 1 is applied to all UEs in a cell, the PDCCH may
not be correctly demodulated by UEs located at a medium distance or far
from the cell center.
By default, the gNodeB selects an appropriate PDCCH aggregation level based on

the PDCCH channel quality (calculated based on the PDSCH SINR) and the PDCCH
block error rate (BLER). The target PDCCH BLER is specified by the
NRDUCellPdcch.PdcchBlerTarget parameter.
The AGG_LVL_INIT_SELECT_OPT_SW option of the

NRDUCellPdcch.PdcchAlgoEnhSwitch parameter determines whether to enable
PDCCH initial aggregation level selection optimization. When this option is
selected, the gNodeB optimizes PDCCH initial aggregation level selection based on
uplink measurement information and cell load information. Under desirable
channel conditions and heavy cell load, the gNodeB lowers the PDCCH
aggregation level to increase the number of UEs supported by PDCCH resources.

(2020-01-20)
5G RAN
PDCCH Modulation Scheme

The modulation scheme quadrature phase shift keying (QPSK) is applied on the
PDCCH.
PDCCH Frequency-Domain Resource Range

When the PDCCH rate matching function is disabled, each symbol of the PDCCH
in a cell spreads over a full bandwidth.
When the PDCCH rate matching function is enabled, the frequency-domain
resources for each symbol of the PDCCH in a cell are specified by the
NRDUCellPdcch.OccupiedRbNum parameter.
● When the value of the NRDUCellPdcch.OccupiedRbNum parameter is 0 or
greater than or equal to the downlink system bandwidth specified by the
NRDUCell.DlBandwidth parameter, the PDCCH occupies a full bandwidth.
● If the value of the NRDUCellPdcch.OccupiedRbNum parameter is greater
than 0 and is less than the downlink system bandwidth specified by the
NRDUCell.DlBandwidth parameter, the frequency-domain resources for the
PDCCH are specified by the NRDUCellPdcch.OccupiedRbNum parameter.
– A smaller value of this parameter allows the PDCCH to occupy fewer
frequency-domain resources in a cell. This leads to more available
resources for the PDSCH and larger PDSCH capacity improvement.
– A larger value of this parameter leads to the opposite effects.
The NRDUCellPdcch.OccupiedRbNum parameter needs to be configured
based on UE distribution in a cell, to adapt to uplink and downlink DCI-
indicated scheduling and prevent access failures or service drops caused by
scheduling failures. For details, see Scheduling.
For more information on the PDCCH rate matching function, see Scheduling.
5.2.1 Benefits
PDCCH channel management enables PDCCH resources to be properly used to
5.2.2 Impacts
Network Impacts
● After PDCCH symbol number adaptation takes effect, the changes in the
number of PDCCH symbols causes RRC reconfiguration for all UEs. This may
increase the service drop rate.
● After PDCCH symbol number adaptation takes effect, the increase in the
number of symbols occupied by the PDCCH, for example, from 1 to 2, has the
following impacts:

(2020-01-20)
5G RAN
– Available CCEs increase, and the number of UEs scheduled in uplink in

each TTI (N.User.Schedule.Ul.Sum) and the number of UEs scheduled in
downlink in each TTI (N.User.Schedule.Dl.Sum) may increase. In
enhanced Mobile Broadband (eMBB), the uplink and downlink PRB usage
and cell throughput may increase, and the packet delay decreases.
– An increased number of PDCCH symbols increases available CCEs
(N.CCE.Avail.Avg) and may decrease the CCE usage (N.CCE.Used.Avg/
N.CCE.Avail.Avg).
– An increased number of PDCCH symbols decreases the number of PDSCH
symbols. In the case of PDSCH congestion not accompanied by PDCCH
congestion, throughput may decrease, and the packet delay increases.
● The decrease in the number of symbols occupied by the PDCCH, for example,
from 2 to 1, has the following impacts:
– Available CCEs decrease, and the number of UEs scheduled in uplink in
each TTI (N.User.Schedule.Ul.Sum) and the number of UEs scheduled in
downlink in each TTI (N.User.Schedule.Dl.Sum) may decrease. In eMBB,
the uplink and downlink PRB usages may decrease, and the packet delay
increases.
– The decrease in the number of PDCCH symbols causes available CCEs
(N.CCE.Avail.Avg) to decrease and may increase the CCE usage
(N.CCE.Used.Avg/N.CCE.Avail.Avg).
– A decreased number of PDCCH symbols increases the number of PDSCH
symbols. In the case of PDSCH congestion not accompanied by PDCCH
congestion, throughput may increase, and the packet delay decreases.

(2020-01-20)
5G RAN
Function Impacts
Function Function Switch Refer Description
Name ence
PDCCH rate PDCCH_RATEMA Sched When the PDCCH rate matching

matching TCH_SW option uling function is enabled, it is
of the recommended that the
NRDUCellPdsch. NRDUCellPdcch.UlMaxCcePct
RateMatchSwitc parameter (specifying the maximum
h parameter percentage of uplink available CCEs)
be set to 50.
● If this parameter is set to a value
less than 50, the CCEs used for
DCI containing uplink scheduling
information may be insufficient.
This can cause transmission of
the DCI containing uplink
scheduling information to fail,
resulting in resynchronization
failures. As a result, RRC
reconfiguration is repeatedly
triggered over the air interface.
● If this parameter is set to a value
greater than 50, the CCEs used
for DCI containing downlink
scheduling information may be
insufficient, thereby decreasing
downlink throughput.
5.3 Requirements
5.3.1 Licenses
5.3.2 Software
None

None

(2020-01-20)
5G RAN
5.3.3 Hardware
Base Station Models

Boards
RF Modules
5.3.4 Others
None

Parameter Parameter ID Option Setting Notes

Name
Occupied NRDUCellPdcch None Set this parameter to its

Symbol .OccupiedSymb recommended value.
Number olNum
Uplink NRDUCellPdcch None Set this parameter based on
Maximum .UlMaxCcePct the proportions of uplink UEs
CCE and downlink UEs.
Percentage

(2020-01-20)
5G RAN
Parameter Parameter ID Option Setting Notes

Name
Number of NRDUCellPdcch None This parameter is configurable

Occupied .OccupiedRbNu when the
RBs m PDCCH_RATEMATCH_SW
option of the
NRDUCellPdsch.RateMatchS
witch parameter is selected.
Set this parameter as
required.
PDCCH BLER NRDUCellPdcch None Set this parameter as

Target .PdcchBlerTarge required.
t
PDCCH NRDUCellPdcch UL_DL_CCE_ Set this parameter to its
Algorithm .PdcchAlgoSwit RATIO_ADAP recommended value.
Switch ch T_SW
PDCCH NRDUCellPdcch UE_PDCCH_S Set this parameter to its

Algorithm .PdcchAlgoSwit YM_NUM_A recommended value.
Switch ch DAPT_SW
PDCCH NRDUCellPdcch AGG_LVL_INI Set this parameter to its

Algorithm .PdcchAlgoEnhS T_SELECT_OP recommended value.
Enhancemen witch T_SW
t Switch

Not involved

//Setting the number of PDCCH symbols to 2 for a cell (required when PDCCH symbol number adaptation
is disabled)
MOD NRDUCELLPDCCH: NRDUCELLID=0,OccupiedSymbolNum=2SYM;
//Setting the maximum percentage of uplink available CCEs to 50% for a cell
MOD NRDUCELLPDCCH: NRDUCELLID=0,UlMaxCcePct=50;
//Configuring a full bandwidth for the PDCCH for a cell in the frequency domain
MOD NRDUCELLPDCCH: NRDUCELLID=0,OccupiedRbNum=0;
//Configuring the target PDCCH BLER
MOD NRDUCELLPDCCH: NRDUCELLID=0, PdcchBlerTarget=3;
//Enabling PDCCH uplink-to-downlink CCE ratio adaptation
MOD NRDUCELLPDCCH: NRDUCELLID=0, PdcchAlgoSwitch=UL_DL_CCE_RATIO_ADAPT_SW-1;
//Enabling UE-specific PDCCH symbol number adaptation
MOD NRDUCELLPDCCH: NRDUCELLID=0, PdcchAlgoExtSwitch=UE_PDCCH_SYM_NUM_ADAPT_SW-1;
//Enabling initial aggregation level selection optimization
MOD NRDUCELLPDCCH: NRDUCELLID=0, PdcchAlgoEnhSwitch=AGG_LVL_INIT_SELECT_OPT_SW-1;

Not involved

(2020-01-20)
5G RAN


This function is a basic function and takes effect by default. Activation verification
is not required.


(2020-01-20)
5G RAN
Description 6 PUCCH Channel Management
6 PUCCH Channel Management
6.1 Principles
The PUCCH carries uplink control information (UCI), which contains the following:
● Acknowledgement (ACK)/Negative acknowledgement (NACK) feedback
Hybrid automatic repeat request (HARQ) ACK/NACK feedback for PDSCH
demodulation
● Channel state information (CSI)
CSI-RS measurement results, such as CQI, precoding matrix indication (PMI),
and rank indication (RI)
CSI-RS refers to CSI-RS for channel measurement (CSI-RS for CM), which is used for
downlink channel state measurements. For more information on CSI-RS for CM, see 8
CSI-RS Resource Management.
● Uplink scheduling request (SR)
Resource request for PUSCH scheduling
UCI formats include format 0, format 1, format 2, format 3, and format 4. For
more information, see section 6.3 "Uplink control information" in 3GPP TS 38.212
(Release 15).
PUCCH channel management works as follows:
1. The gNodeB performs cell-specific PUCCH configuration. For more
information, see Cell-specific PUCCH Configuration.
2. The gNodeB allocates resources to UEs based on cell-specific PUCCH
configurations. For more information, see PUCCH Resource Allocation.
3. Based on the resources allocated by the gNodeB, UEs select a proper resource
unit for UCI transmission over the PUCCH. For more information, see
Resource Unit Selection.

(2020-01-20)
5G RAN
Cell-specific PUCCH Configuration

The PUCCH's time-frequency resources are configured on a per cell basis. Cell-
specific PUCCH time-frequency formats include short formats and long formats,
depending on the setting of the NRDUCellPucch.StructureType parameter.
In low frequency bands, both short formats and long formats are supported. Long
formats are recommended and used by default in low frequency bands. This is
because long formats provide better coverage than short formats and can
guarantee the maximum number of supported UEs, whereas short formats do not
provide such guarantee.
In high frequency bands, only short formats are supported. This is because the
default parameter settings of short formats can guarantee the maximum number
of supported UEs owing to the limitations on analog beams.
Short format
The short PUCCH can use format 0 or format 2, with time-frequency formats
illustrated in Figure 6-1 and Figure 6-2.
When a short format is used in low frequency bands, the time-domain resources
are specified by the NRDUCellPucch.ShortPucchSymbolNum parameter and this
parameter can only be set to SYMBOL1 or SYMBOL2, and a full bandwidth is
used in the frequency domain.
In high frequency bands, only short formats are supported. In the time domain,
static configuration and dynamic configuration are supported. In the frequency
domain, a full bandwidth is supported.
● Static configuration: If the PUCCH_RES_ADAPTIVE_SWITCH option of the
NRDUCellPucch.PucchAlgoSwitch parameter is deselected, the time-domain
resources are specified by the NRDUCellPucch.ShortPucchSymbolNum
parameter.
● Dynamic configuration: If the PUCCH_RES_ADAPTIVE_SWITCH option of the
NRDUCellPucch.PucchAlgoSwitch parameter is selected, the number of
symbols occupied by the PUCCH in the time domain is dynamically adjusted
based on the number of UEs and load.

(2020-01-20)
5G RAN
Figure 6-1 Per-RB time-frequency format in format 0
Long format
The long PUCCH can use format 1, format 3, or format 4, with time-frequency
formats illustrated in Figure 6-3 and Figure 6-4. In format 1, format 3, and
format 4, the number of symbols is always 14 in the time domain, and dynamic
and static configuration are supported in the frequency domain.
● If the PUCCH_RBRES_ADAPTIVE_SWITCH option of the

NRDUCellPucch.PucchAlgoSwitch parameter is selected, the number of RBs
used by the PUCCH in the frequency domain is dynamically adjusted based on
the number of UEs and load.
● If the PUCCH_RBRES_ADAPTIVE_SWITCH option of the
NRDUCellPucch.PucchAlgoSwitch parameter is deselected, the frequency-
domain resources are specified by the following parameters:

(2020-01-20)
5G RAN
– Number of RBs for ACK/NACK feedback
▪ NRDUCellPucch.Format1RbNum
– Number of dedicated RBs for CSI reporting
▪ NRDUCellPucch.CsiDedicatedRbNum
▪ NRDUCellPucch.Format4CsiDedicatedRbNum
The total number of RBs configured for the PUCCH is limited in specific
scenarios. During configuration, the number of RBs in each format must be
properly planned. The scenarios are as follows:
– For a 20 MHz NR TDD cell, no more than 26 RBs can be configured for
the PUCCH.
– For an SUL cell not enabled with spectrum sharing, if the cell bandwidth
is 10 MHz, 15 MHz, or 20 MHz, no more than 30 RBs can be configured
for the PUCCH.

(2020-01-20)
5G RAN
Figure 6-4 Per-RB time-frequency format in format 3 or format 4
PUCCH Resource Allocation

According to specifications, PUCCH resources can be configured through RRC
signaling, semi-persistently (for example, through MAC CE activation and
deactivation), or dynamically (for example, through PDCCH DCI). MAC CE is short
for Media Access Control Control Element.
According to specifications, the following restrictions apply:
● PUCCH resources for SR transmission can be configured only through RRC
signaling.
● PUCCH resources for periodic CSI transmission can be configured through RRC
signaling and semi-persistently.
● PUCCH resources for ACK and NACK transmission can be configured through
RRC signaling and dynamically.
The current version is subject to the following implementation restrictions:
● PUCCH resources for SR transmission can only be statically configured.
Static PUCCH resource allocation for SR transmission works as follows: The
gNodeB allocates a UE one resource set, which is signaled by an IE in a
higher-layer RRC message and provides configurations such as the time-
frequency position, index ID, start symbol, and number of symbols.
The SR period can be statically configured or dynamically adjusted.
– If the SR_PERIOD_ADAPT_SWITCH option of the
NRDUCellPucch.SrResoureAlgoSwitch parameter is deselected, the SR
period is statically specified by the NRDUCellPucch.SrPeriod parameter.
– If the SR_PERIOD_ADAPT_SWITCH option of the
NRDUCellPucch.SrResoureAlgoSwitch parameter is selected, the
gNodeB dynamically adjusts the SR period based on the number of UEs.
If the number of admitted UEs in a cell is small, a short period is
configured for newly admitted UEs. As the number of admitted UEs
increases, the gNodeB configures a long SR period for some UEs that
originally used shorter periods. This mechanism ensures that the number

(2020-01-20)
5G RAN
of admitted UEs can reach the maximum number allowed for the cell.
The maximum SR period for UEs is 80 ms.
● PUCCH resources for periodic CSI transmission can only be statically
configured, meaning semi-persistent PUCCH resource allocation is not
supported.
Static PUCCH resource allocation for periodic CSI transmission works as
follows: The gNodeB allocates a UE one resource set, which is signaled by an
IE in a higher-layer RRC message and provides configurations such as the
time-frequency position, index ID, start symbol, and number of symbols.
For low-frequency cells, the CSI reporting period can be statically configured
or dynamically adjusted.
– Static configuration: If the CSI_REPORT_PERIOD_ADAPT_SWITCH option
of the NRDUCellPucch.CsiResoureAlgoSwitch parameter is deselected,
the CSI reporting period is statically specified by the
NRDUCellPucch.CsiReportPeriod parameter.
For FDD cells, the value of this parameter or the value of
NRDUCellCsirs.CsiPeriod is used as the CSI reporting period, whichever is
larger.
For TDD cells, the value of this parameter or the value of
NRDUCellCsirs.CsiPeriod is used as the CSI reporting period, whichever is
larger.
For SUL cells, the value of this parameter or the value of
NRDUCellCsirs.CsiPeriod divided by two is used as the CSI reporting
period, whichever is larger.
– Static configuration: If the CSI_REPORT_PERIOD_ADAPT_SWITCH option
of the NRDUCellPucch.CsiResoureAlgoSwitch parameter is selected, the
gNodeB dynamically adjusts the CSI reporting period based on the
number of UEs. If the number of admitted UEs in a cell is small, a short
period is configured for newly admitted UEs. As the number of admitted
UEs increases, the gNodeB configures a long CSI reporting period for
some UEs that originally used shorter periods. This mechanism ensures
that the number of UEs periodically transmitting CSI in a cell can reach
the maximum value allowed for the cell. The maximum CSI reporting
period for UEs is 160 ms.
In high-frequency cells, CSI can only be aperiodically reported. Aperiodic CSI is
transmitted on the PUSCH. For details about the PUSCH, see Scheduling.
● PUCCH resources for ACK/NACK transmission can be dynamically configured.
Dynamic PUCCH resource allocation for ACK/NACK transmission works as
follows:
a. The gNodeB allocates a UE multiple (four defined in specifications and
two supported in the current version) resource sets, which are signaled by
an IE in a higher-layer RRC message. Each resource set includes up to
eight PUCCH resources, with each providing configurations such as the
time-frequency position, index ID, start symbol, and number of symbols.
b. Based on PDSCH data scheduling, the gNodeB allocates one set of idle
PUCCH resources to a UE to transmit HARQ feedback, and signals the
resource set index ID through the DCI.

(2020-01-20)
5G RAN
For more information on SR resource configuration, see

"SchedulingRequestResourceConfig" in 3GPP TS 38.331 (Release 15).
For resource set definitions, see "PUCCH-Config" in 3GPP TS 38.331 (Release 15).
Resource Unit Selection

A UE selects appropriate time-frequency resources to transmit UCI based on the
time-frequency resource range indicated in the resource set. The UE selects a
resource unit based on the PUCCH's time-frequency format.
● As stipulated in specifications, the resource unit is one RB in format 0 (short

format).
● As stipulated in specifications, the resource unit ranges from one RB to 16 RBs
in format 2 (short format).
● As stipulated in specifications, the resource unit is one RB in format 1 (long
format).
● As stipulated in specifications, the resource unit is 1, 2, 3, 4, 5, 6, 8, 9, 10, 12,
15, or 16 RBs in format 3 (long format). In the current version, the resource
unit is only one RB in format 3 (long format).
● As stipulated in specifications, the resource unit is one RB in format 4 (long
format).
PUCCH Modulation Scheme

In the current version, the short PUCCH uses format 0 or format 2. No modulation
scheme is used in format 0. The modulation scheme QPSK is used in format 2.
In the current version, the long PUCCH uses format 1, format 3, or format 4. The
modulation schemes binary phase shift keying (BPSK) and QPSK are respectively
used in format 1 with one bit and format 1 with two bits. The modulation scheme
QPSK is used in format 3 and format 4.
6.2.1 Benefits
PUCCH channel management enables PUCCH resources to be properly used to
6.2.2 Impacts
Network Impacts
None

(2020-01-20)
5G RAN
Function Impacts
Function Function Switch Reference Description
Name
High-speed NRDUCell.HighSp High Speed Only long PUCCH time-

Railway eedFlag Mobility frequency formats are
Superior supported by high-speed cells
Experience (for which
NRDUCell.HighSpeedFlag is
set to HIGH_SPEED).
FDD cell NRDUCell.Duplex Cell Only long PUCCH time-

Mode Manageme frequency formats are
nt supported by FDD cells (for
which
NRDUCell.DuplexMode is set
to CELL_FDD).
SUL cell NRDUCell.Duplex Cell Only long PUCCH time-

Mode Manageme frequency formats are
nt supported by SUL cells (for
which
NRDUCell.DuplexMode is set
to CELL_SUL).
High- NRDUCell.Freque Cell Only short PUCCH time-

frequency ncyBand Manageme frequency formats (specified
cell nt by
NRDUCellPucch.StructureTyp
e) are supported by high-
frequency cells (for which
NRDUCell.FrequencyBand is
set to N257, N258, N260, or
N261).
Intra-band INTRA_BAND_CA Carrier If low-frequency cells use

CA _SW option of the Aggregatio short formats (specified by
NRDUCellAlgoSw n NRDUCellPucch.StructureTyp
itch.CaAlgoSwitc e), intra-band CA does not
h parameter take effect and therefore long
formats must be used.
Short formats (specified by
e), if used in high-frequency
cells, do not affect whether
intra-band CA takes effect.

(2020-01-20)
5G RAN

Name
Intra-FR INTRA_FR_INTER Carrier If low-frequency cells use

inter-band _BAND_CA_SW Aggregatio short formats (specified by
CA option of the n NRDUCellPucch.StructureTyp
NRDUCellAlgoSw e), intra-FR inter-band CA
itch.CaAlgoSwitc does not take effect and
h parameter therefore long formats must
be used.
High-frequency cells do not
support intra-FR inter-band
CA.

(2020-01-20)
5G RAN

Name
BWP NRDUCellUePwrS UE Power When BWP takes effect, the

aving.BwpPwrSa Saving cell-specific PUCCH time-
vingSw frequency formats (specified
by
e) can only be long formats.
When the
PUCCH_RBRES_ADAPTIVE_S
WITCH option of the
NRDUCellPucch.PucchAlgoS
witch parameter is deselected:
● In NSA networking, if
NRDUCellPucch.Format1R
bNum is set to 2, BWP2
(narrow bandwidth) cannot
be allocated to UEs.
● In SA networking, if the
INIT_BWP_FULL_BW_SW
option of the
NRDUCellAlgoSwitch.Bwp
ConfigPolicySwitch
parameter is selected and
the
NRDUCellPucch.Format1R
bNum parameter is set to
2, BWP2 (narrow
bandwidth) cannot be
allocated to UEs.
If the
PUCCH_RBRES_ADAPTIVE_S
WITCH option of the
NRDUCellPucch.PucchAlgoS
witch parameter is deselected
and the
NRDUCellPucch.Format3RbN
um parameter is set to 2,
BWP2 (narrow bandwidth)
cannot be allocated to UEs.
6.3 Requirements
6.3.1 Licenses

(2020-01-20)
5G RAN
6.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
None

Functio Function Refere Description
n Name Switch nce
High- NRDUCell.High High High-speed Railway Superior Experience

speed SpeedFlag Speed is mutually exclusive with the following
Railway Mobilit PUCCH sub-functions:
Superior y ● SR period adaptation (specified by the
Experie SR_PERIOD_ADAPT_SWITCH option
nce of the
NRDUCellPucch.SrResoureAlgoSwitc
h parameter)
● RB adaptation in long formats
(specified by the
PUCCH_RBRES_ADAPTIVE_SWITCH
option of the
NRDUCellPucch.PucchAlgoSwitch
parameter)
● Format 4 (long format) (specified by
NRDUCellPucch.Format4RbNum or
NRDUCellPucch.Format4CsiDedicate
dRbNum. The value RB0 indicates
that this function does not take
effect.)
● CSI reporting period adaptation
(controled by the
CSI_REPORT_PERIOD_ADAPT_SWITC
H option of the
NRDUCellPucch.CsiResoureAlgoS-
witch parameter)
LTE FDD LTE_NR_FDD_S LTE LTE FDD and NR Flash Dynamic
and NR PCT_SHR_SW FDD Spectrum Sharing is mutually exclusive
Flash option of the and NR with RB adaptation in long PUCCH
Dynami NRDUCellAlgo Spectru formats (specified by the
c Switch.Spectru m PUCCH_RBRES_ADAPTIVE_SWITCH
Spectru mCloudSwitch Sharin option of the
m parameter g NRDUCellPucch.PucchAlgoSwitch
Sharing parameter).

(2020-01-20)
5G RAN
6.3.3 Hardware
Base Station Models

Boards
RF Modules
6.3.4 Others
Support for format 4 is optional for UEs. If format 4 is configured, UEs must
support this format, which is indicated by the pucch-F4-WithFH IE in the
UECapabilityInformation message over the Uu interface.


Name
Structure NRDUCellPucch.S Set this parameter based on the network

Type tructureType plan.
Short PUCCH NRDUCellPucch.S This parameter must be specified if a short

Symbol hortPucchSymbol time-frequency format is used. Retain the
Number Num default value.

(2020-01-20)
5G RAN

Name
Format1 RB NRDUCellPucch.F This parameter must be specified if a long

Number ormat1RbNum time-frequency format is used. Retain the
default value.

Number ormat3RbNum time-frequency format is used.
In low-speed TDD cells, if RB adaptation is
disabled and mainstream UEs support
format 4, it is recommended that this
parameter be modified to RB8.
It is good practice to retain the default
value in other scenarios.

Number ormat4RbNum time-frequency format is used.
In low-speed TDD cells, if RB adaptation is
format 4, it is recommended that this
parameter be modified to RB6.
Format3 CSI- NRDUCellPucch. This parameter must be specified if a long

dedicated RB CsiDedicatedRbN time-frequency format is used. Retain the
Number um default value.

(2020-01-20)
5G RAN

Name
Format4 CSI- NRDUCellPucch.F This parameter must be specified if a long

dedicated RB ormat4CsiDedica time-frequency format is used.
Number tedRbNum In low-speed TDD cells, if RB adaptation is
format 4, the recommended parameter
settings (based on the recommended
CsiReportPeriod value of SLOT80) are as
follows:
● If the UBBPfw is used, it is good
practice to set this parameter to RB2 in
cases where the number of UEs is less
than or equal to 96, and RB4 in cases
where the number of UEs is greater
than 96.
● If the UBBPg is used, it is good practice
to set this parameter to RB2 in cases
where the number of UEs is less than or
equal to 96, RB4 in cases where the
number of UEs is greater than 96 but
less than or equal to 160, RB6 in cases
where the number of UEs is greater
than 160 but less than or equal to 224,
RB8 in cases where the number of UEs
is greater than 224.

(2020-01-20)
5G RAN

Name
SR Perioda NRDUCellPucch.S The following are recommended SR period

rPeriod settings depending on the number of UEs:
For TDD cells established on the UBBPfw:
● If the number of UEs is less than or
equal to 50, SLOT20 is recommended.
● If the number of UEs is greater than 50
but less than or equal to 100, SLOT40 is
recommended.
● If the number of UEs is greater than
100 but less than or equal to 200,
SLOT80 is recommended.
200, SLOT160 is recommended.
For low-frequency TDD cells established on
the UBBPg:
For TDD high-frequency cells established
on the UBBPg:
recommended.
recommended.
but less than or equal to 128, SLOT320
is recommended.
For FDD cells:

(2020-01-20)
5G RAN

Name

SR Resource NRDUCellPucch.S The SR_PERIOD_ADAPT_SWITCH option

Algo Switch rResoureAlgoSwi of this parameter specifies whether to
tch enable SR period adaptation.
● It is recommended that SR period
adaptation be enabled for low-speed
cells (for which
NRDUCell.HighSpeedFlag is set to
LOW_SPEED) to adapt to different UE
quantities.
● SR period adaptation is not supported
in high-speed cells (for which
NRDUCell.HighSpeedFlag is set to
HIGH_SPEED).
PUCCH NRDUCellPucch.P The PUCCH_RES_ADAPTIVE_SWITCH

Algorithm ucchAlgoSwitch option of this parameter specifies whether
Switch to enable symbol adaptation in short
PUCCH formats. This function applies only
in high frequency bands. Use the
recommended setting for this option.
The PUCCH_RBRES_ADAPTIVE_SWITCH
option of this parameter specifies whether
to enable RB adaptation in long PUCCH
formats. This option applies only to low-
speed TDD cells and FDD/SUL cells not
enabled with LTE and NR sharing. Use the
recommended setting for this option.
CSI Report NRDUCellPucch. Set this parameter to its recommended

Period CsiReportPeriod value.
CSI Resource NRDUCellPucch. Set this parameter to its recommended

Algo Switch CsiResoureAlgoS- value.
witch
a: The actual SR period depends on SCS and the number of slots. For example, 1
ms is equal one slot, two slots, four slots, and eight slots when SCS is 15 kHz, 30
kHz, 60 kHz, and 120 kHz, respectively. For more information, see
"SchedulingRequestResourceConfig field descriptions" in 3GPP TS 38.331
(Release 15).

(2020-01-20)
5G RAN

Not involved

Command examples in TDD
//Configuring the PUCCH format
MOD NRDUCELLPUCCH: NRDUCELLID=0, StructureType=LONG_STRUCTURE;
//Configuring the number of symbols of the short PUCCH for a cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, ShortPucchSymbolNum=SYMBOL1;
//Configuring the number of RBs used in format 1 for a cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, Format1RbNum=RB4;
//Configuring SR period adaptation
MOD NRDUCELLPUCCH: NrDuCellId=0, SrResoureAlgoSwitch=SR_PERIOD_ADAPT_SWITCH-1;
//Configuring the SR period (required when SR period adaptation is disabled)
MOD NRDUCELLPUCCH: NrDuCellId=0, SrPeriod=SLOT40;
//Configuring the number of CSI-dedicated RBs for a cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, CsiDedicatedRbNum=RB2, Format4CsiDedicatedRbNum=RB0;
//Configuring symbol adaptation in a short format for a high-frequency cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, PucchAlgoSwitch=PUCCH_RES_ADAPTIVE_SWITCH-1;
//Configuring PUCCH RB adaptation for a low-frequency cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, PucchAlgoSwitch=PUCCH_RBRES_ADAPTIVE_SWITCH-1;
//Configuring the CSI reporting period
MOD NRDUCELLPUCCH: NrDuCellId=0, CsiReportPeriod=SLOT80;
//Configuring CSI reporting period adaptation
MOD NRDUCELLPUCCH: NrDuCellId=0, CsiResoureAlgoSwitch= CSI_REPORT_PERIOD_ADAPT_SWITCH-1;
Command examples in FDD

//Configuring the PUCCH format
MOD NRDUCELLPUCCH: NRDUCELLID=0, StructureType=LONG_STRUCTURE;
//Configuring the number of symbols of the short PUCCH for a cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, ShortPucchSymbolNum=SYMBOL1;
//Configuring SR period adaptation
MOD NRDUCELLPUCCH: NrDuCellId=0, SrResoureAlgoSwitch=SR_PERIOD_ADAPT_SWITCH-1;
//Configuring the SR period (required when SR period adaptation is disabled)
MOD NRDUCELLPUCCH: NrDuCellId=0, SrPeriod=SLOT40;
//Configuring the number of CSI-dedicated RBs for a cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, CsiDedicatedRbNum=RB4;
//Configuring PUCCH RB adaptation for a low-frequency cell
MOD NRDUCELLPUCCH: NRDUCELLID=0, PucchAlgoSwitch=PUCCH_RBRES_ADAPTIVE_SWITCH-1;
//Configuring the CSI reporting period
MOD NRDUCELLPUCCH: NrDuCellId=0, CsiReportPeriod=SLOT80;
//Configuring CSI reporting period adaptation
MOD NRDUCELLPUCCH: NrDuCellId=0, CsiResoureAlgoSwitch=CSI_REPORT_PERIOD_ADAPT_SWITCH-1;

Not involved

(2020-01-20)
5G RAN


Step 1 Start Uu signaling tracing on the MAE-Access as follows: Log in to the MAE-Access
and choose Monitor > Signaling Trace > Signaling Trace Management. On the
displayed page, choose Trace Type > NR > Application Layer > Uu Interface
Trace.
Step 2 Enable a UE to access the network. In SA networking, check the traced
RRCReconfiguration message as shown in Figure 6-5. Check the fields in the
PUCCH-Config IE. If format information is present in the PUCCH-Resource field,
the indicated format has taken effect.
In NSA networking, check the SgNB Addition Request Acknowledge message. Check the
same IEs as described in SA networking.
Figure 6-5 RRCReconfiguration message tracing report (SA networking)
----End


(2020-01-20)
5G RAN
Description 7 PRACH Channel Management
7 PRACH Channel Management
7.1 Principles
7.1.1 RA Preamble
7.1.1.1 Overview
During RA, a UE needs to send an RA preamble (signal) on the PRACH. RA
preamble formats fall into two types: long format and short format. An RA
preamble is a pulse signal. In the time domain, it consists of a TCP, a TSEQ, and a
TGT, as shown in Figure 7-1. TCP denotes a cyclic prefix, TSEQ a preamble sequence,
and TGT the guard time. In the frequency domain, an RA preamble occupies
multiple subcarriers, specifically 839 subcarriers for a long preamble and 139
subcarriers for a short preamble.
Figure 7-1 RA preamble format
Table 7-1 and Table 7-2 list the mapping among format indexes, preamble
lengths ( ), and PRACH SCS ( ) supported by the gNodeB in the current
version. For NR TDD, the long format is supported only in low frequency bands.

(2020-01-20)
5G RAN
The short format is supported in both low and high frequency bands. For NR FDD,
only the long format is supported. For more information on preambles formats,
see section 6.3.3.1 "Sequence generation" in 3GPP TS 38.211 (Release 15).
Table 7-1 Long preamble
Format
0 839 1.25 kHz
Table 7-2 Short preamble
Format
C2 139 kHz
In the current version, the preamble format and PRACH SCS used by the gNodeB
are determined by the duplex mode (NRDUCell.DuplexMode), uplink-downlink
slot assignment (NRDUCell.SlotAssignment), PUSCH SCS
(NRDUCell.SubcarrierSpacing), cell radius (NRDUCell.CellRadius), and PRACH
configuration index (NRDUCellPrach.PrachConfigurationIndex), as listed in
Table 7-3. The configurations in the fifth and sixth rows are supported only in NR
TDD high frequency bands.
Table 7-3 Preamble formats and PRACH SCS used by the gNodeB
Duplex UL-DL Slot PUSCH Cell Radius PRACH Prea PRACH SCS
Mode Assignment SCS Configuratio mble
n Index Form
at
CELL_FDD Not involved 15 kHz ≤ 14.5 km 0 to 21, 0 1.25 kHz

65535
CELL_TDD 4_1_DDDSU 30 kHz ≤ 9.65 km 200, 202, 210, C2 15 kHz

65535
CELL_TDD 8_2_DDDDDDD 30 kHz ≤ 14.5 km 0 to 7, 12, 17, 0 1.25 kHz

SUU or 65535
7_3_DDDSUDD
SUU
CELL_TDD 8_2_DDDDDDD 30 kHz ≤ 9.65 km 200, 202, 210 C2 15 kHz

SUU
or
7_3_DDDSUDD
SUU
CELL_TDD 4_1_DDDSU 120 kHz ≤ 2.41 km 187, 65535 C2 60 kHz

(2020-01-20)
5G RAN
Duplex UL-DL Slot PUSCH Cell Radius PRACH Prea PRACH SCS
Mode Assignment SCS Configuratio mble
n Index Form
at
CELL_TDD 4_1_DDDSU 120 kHz ≤ 1.16 km 189 C2 120 kHz
CELL_SUL Not involved 15 kHz ≤ 14.5 km 0 to 21, 0 1.25 kHz

65535
The PRACH configuration index (specified by the

NRDUCellPrach.PrachConfigurationIndex parameter) depends on factors such as the
networking, system frequency band, duplex mode, slot assignment, and cell radius. For
more information, see the recommended values of the
NRDUCellPrach.PrachConfigurationIndex parameter. For more information on the PRACH
configuration index, see 3GPP TS 38.211 (Release 15).
7.1.1.2 Preamble Sequence Generation

Preamble sequences are generated through cyclic shifts of Zadoff-Chu (ZC) root
sequences.
● The start logical ZC root sequence index is specified by the

NRDUCell.LogicalRootSequenceIndex parameter. For a long preamble, the
parameter value cyclically ranges from 0 to 837. For a short preamble, the
parameter value cyclically ranges from 0 to 137.
The following are examples:
– For a long preamble, logical index 837 is followed by index 0.
– For a short preamble, logical index 137 is followed by index 0.
● The number of cyclic shifts is determined by the gNodeB based on the cell
type and radius.
Each cell can be configured with a maximum of 64 preambles. If fewer than 64

preamble sequences are generated from a single ZC root sequence, subsequent ZC
root sequences are used until 64 preambles are generated. For more information
on preamble sequence generation, see section 6.3.3.1 "Sequence generation" in
3GPP TS 38.211 V2.0.0. The logical ZC sequence index and the number of cyclic
shifts are indicated by the RACH-ConfigCommon IE.
In SA networking, the RACH-ConfigCommon IE is carried in SIB1. In NSA networking, the

RACH-ConfigCommon IE is carried in the RRCConnectionReconfiguration message.
7.1.1.3 Preamble Sequence Grouping

A cell has 64 preamble sequences, which are used during requests for system
information and RA.

(2020-01-20)
5G RAN
● If on-demand system information transmission is enabled for a cell, some

preamble sequences are used during requests for system information, and
other preamble sequences are used during RA.
● If on-demand system information transmission is not enabled for a cell, all
the preamble sequences are used during RA.
For more information on system information transmission policies of cells, see 5G

Networking and Signaling.
Based on RA contention, the preamble sequences for RA are classified into random
preamble sequences and dedicated preamble sequences, as Figure 7-2 illustrates.
The proportion of random preamble sequences to random and dedicated
preamble sequences can be configured by the NRDUCellPrach.CbraPreamblePct
parameter.
● If this parameter is set to a value other than 255, the actual proportion of
random preamble sequences is the value of this parameter.
● If this parameter is set to 255, the actual proportion of random preamble
sequences is 82% for low-speed cells (for which NRDUCell.HighSpeedFlag is
set to LOW_SPEED) or 60% for high-speed cells (for which
NRDUCell.HighSpeedFlag is set to HIGH_SPEED).
Random preambles are used for contention-based RA. Dedicated preambles are used for
non-contention-based RA. For more information on contention-based and non-contention-
based RA, see 5G Networking and Signaling.
The number of random preambles varies with RA scenarios and is indicated by

totalNumberOfRA-Preambles in the RACH-ConfigCommon IE. For more
information, see section 6.3.2 "Radio resource control information elements" in
3GPP TS 38.331 V2.0.0.
Figure 7-2 Preamble sequence grouping

(2020-01-20)
5G RAN
7.1.2 Time-Frequency Resources for RA

A UE initiates RA using specific time-frequency resources (namely, PRACH). When
a UE initiates an access request over the PRACH, a preamble is transmitted.
Time-Domain Position
The time-domain position of the PRACH refers to the frame number and slot
number of a preamble. The frame number and slot number are determined by the
PRACH configuration index. For more information, see section 6.3.3.2 "Mapping to
physical resources" in 3GPP TS 38.211 V2.0.0. The PRACH configuration index used
by the gNodeB is specified by the NRDUCellPrach.PrachConfigurationIndex
parameter.
● If this parameter is not set to 65535, the PRACH configuration index used by
the gNodeB is the value of this parameter. For details about configuration
introduction, see Table 7-3.
● If this parameter is set to 65535, the PRACH configuration index used by the
gNodeB is automatically generated by the gNodeB based on the system
frequency band, duplex mode (NRDUCell.DuplexMode), uplink-downlink slot
assignment (NRDUCell.SlotAssignment), PUSCH SCS
(NRDUCell.SubcarrierSpacing), and cell radius (NRDUCell.CellRadius).
Table 7-4 lists the PRACH configuration indexes that can be used by the
gNodeB in the current version.
Table 7-4 PRACH configuration indexes that can be used by the gNodeB (when
NRDUCellPrach.PrachConfigurationIndex is set to 65535)
Duplex Mode UL-DL Slot PUSCH SCS Cell Radius PRACH
Assignment Configuration Index
CELL_FDD Not involved 15 kHz ≤ 14.5 km 19
CELL_TDD 4_1_DDDSU 30 kHz ≤ 9.65 km 210
CELL_TDD 8_2_DDDDDDDSUU 30 kHz ≤ 14.5 km 17

or
7_3_DDDSUDDSUU
CELL_SUL Not involved 15 kHz ≤ 14.5 km ● SA networking:

19
● NSA networking:
21
● NSA+SA
networking: 21

(2020-01-20)
5G RAN
Frequency-Domain Position
The start frequency-domain position of the PRACH is specified by the
NRDUCell.PrachFreqStartPosition parameter.
● If this parameter is not set to 65535, the start frequency-domain position of

the PRACH is the Xth RB of the initial BWP where X is the value of this
parameter.
● If this parameter is set to 65535, the PRACH is located at the lower end of the
initial BWP. When the long PUCCH is configured in the initial BWP, the PRACH
is adjacent to the long PUCCH. When the long PUCCH is not configured in the
initial BWP, the PRACH is adjacent to the common PUCCH, as shown in
Figure 7-3.
Figure 7-3 Frequency-domain position of the PRACH

(2020-01-20)
5G RAN
For details about the long PUCCH, see 6 PUCCH Channel Management. The
common PUCCH is indicated by pucch-ResourceCommon. For details about the
common PUCCH, see section 9.2.1 "PUCCH Resource Sets" in 3GPP TS 38.213
V15.5.0.
The PRACH occupies multiple PRBs in the frequency domain. The number of PRBs
depends on the preamble length ( ), PRACH SCS ( ), and PUSCH SCS
( ). Table 7-5 lists the number of PRBs supported by the gNodeB in the current
version. For more information on all the numbers of PRBs defined in 3GPP
specifications, see section 6.3.3.2 "Mapping to physical resources" in 3GPP TS
38.211 (Release 15).
Table 7-5 Number of PRBs for the PRACH
for the for the PUSCH Number of PRBs

PRACH for the PRACH
839 1.25 kHz 15 kHz 6
839 1.25 kHz 30 kHz 3
139 15 kHz 30 kHz 6
139 60 kHz 120 kHz 6
139 120 kHz 120 kHz 12
7.1.3 Increasing the PRACH Preamble Detection Threshold

If a UE does not send a preamble but the gNodeB detects a preamble from the
UE, the erroneous detection of the preamble is considered a PRACH false alarm.
The false alarm probability can be reduced by increasing the PRACH preamble
detection threshold through the NRDUCellPrach.PrachThldIncreaseRate
parameter. It is recommended that this parameter be modified when the false
alarm probability of a cell is higher than the expected value.
● A larger value of this parameter results in a lower probability of both
preambles detected and false alarms. It also results in a higher probability of
both missing detection and UE access failures due to weak coverage at the
cell edge.
● A smaller value of this parameter results in a higher probability of both
preambles detected and false alarms. It also results in a lower probability of
both missing detection and UE access failures due to weak coverage at the
cell edge.
For details about false alarms, see section 8.4.1 "PRACH False alarm probability"
in 3GPP TS 38.104 V15.6.0.

(2020-01-20)
5G RAN
7.1.4 PRACH Root Sequence Conflict Detection and Self-

optimization
PRACH preamble sequences are generated through cyclic shifts of ZC root
sequences. Each root sequence can generate multiple preamble sequences. For
more information, see 7.1.1.2 Preamble Sequence Generation.
If the frequency-domain resources of the PRACH in adjacent cells overlap and the
same preamble is used, false alarms or collisions will occur during access request
reception and detection in the cells. See Figure 7-4 and Figure 7-5.
Figure 7-4 False alarms caused by PRACH root sequences
Figure 7-5 Collisions caused by PRACH root sequences
PRACH Root Sequence Conflict Detection

The MAE-Access provides the PRACH root sequence conflict detection function.
This function is used to detect PRACH root sequence conflicts between the serving
cell and neighboring cells. The MAE-Access determines that a PRACH root
sequence conflict occurs when both the following conditions are met:
● The time-frequency resources of the PRACH in the serving cell overlap with
those in neighboring cells.
● Some or all root sequences used by the serving cell are the same as those
used by neighboring cells.
For more information on how to enable PRACH root sequence conflict detection, see MAE
SON Management User Guide.

(2020-01-20)
5G RAN
PRACH Root Sequence Conflict Self-optimization

The MAE-Access provides the PRACH root sequence conflict self-optimization
function. This function is used to resolve PRACH root sequence conflicts between
cells. Once a PRACH root sequence conflict between cells is detected, the MAE-
Access automatically allocates a new PRACH root sequence index (specified by the
NRDUCell.LogicalRootSequenceIndex parameter) and a new PRACH's frequency-
domain start position (specified by the NRDUCell.PrachFreqStartPosition
parameter) to the conflicting cell.
The reallocation causes the cell to automatically restart and become unavailable,
interrupting services of UEs for a short period.
For more information on how to enable PRACH root sequence conflict self-optimization,
see MAE SON Management User Guide.
7.1.5 Optimization of Non-Contention-based RA Beyond Cell

Radius
When a UE initiates a non-contention-based RA beyond the cell radius configured
on the gNodeB (by sending a dedicated preamble), the gNodeB cannot correctly
identify the dedicated preamble. As a result, the non-contention-based RA
procedure fails.
The procedure of non-contention-based RA initiated by a UE beyond the cell
radius is optimized to ensure successful access.
This function is controlled by the CONTENTION_FREE_RA_OPT_SW option of the
NRDUCellPrach.RachAlgoOptSwitch parameter.
This function is recommended when the non-contention-based RA success rate in
a cell is lower than expected. This function takes effect only when both of the
following conditions are met:
● The cell is a normal low-speed cell (this function is not supported in high-
speed railway, tunnel, hyper cell, or CA scenarios.).
● The distance between the UE and the gNodeB is greater than the cell radius
but less than twice the cell radius.
7.2.1 Benefits
PRACH channel management enables PRACH resources to be properly used to

(2020-01-20)
5G RAN
7.2.2 Impacts
Network Impacts
In NSA networking, when the ServingCellConfigCommon IE is updated, UEs re-
access the network, causing transient service interruption. For details, see "Radio
resource control information elements" in 3GPP TS 38.331 (Release 15).
Optimization of non-contention-based RA beyond cell radius may have the

following impacts on KPIs:
● The number of RRC_CONNECTED UEs increases.

● The access or handover delay of UEs beyond the cell radius is longer than that
of common UEs. As a result, the overall access or handover delay may
increase.
● If UEs located beyond the cell radius receive poor coverage, the following
apply:
– If the UEs successfully access the network, uplink and downlink user
experience deteriorates and the service drop rate may increase.
– If the UE access or handover fails, the access or handover success rate
decreases.
Function Impacts
Name
High-speed NRDUCell.HighSpeed High Speed High-speed cells

Railway Flag Mobility (for which
Superior NRDUCell.HighSpe
Experience edFlag is set to
HIGH_SPEED)
support only
PRACH preamble
format C2.
7.3 Requirements
7.3.1 Licenses
None
7.3.2 Software
None

(2020-01-20)
5G RAN

None
7.3.3 Hardware
Base Station Models
Boards
RF Modules
7.3.4 Others
In the case of high-frequency cells in a multi-carrier sector, PRACH channel
resource configurations, such as the PRACH SCS and PRACH configuration index,
must be the same for all the cells in the same sector. For details, see Cell
Management. There are no such requirements in low frequency bands.
For details about the PRACH SCS supported in the current version, see Table 7-3.


(2020-01-20)
5G RAN

Name
CBRA NRDUCellPrach.C Configure this parameter based on the

Preamble braPreamblePct network plan. For details, see 7.1.1.3
Percentage Preamble Sequence Grouping.
PRACH NRDUCell.PrachF Configure this parameter based on the

Frequency reqStartPosition network plan. For details, see 7.1.2 Time-
Start Position Frequency Resources for RA.
PRACH NRDUCellPrach.P Retain the default value. If the false alarm

Threshold rachThldIncreas- probability of a cell is higher than the
Increase Rate eRate expected value, modify this parameter. For
details, see 7.1.3 Increasing the PRACH
Preamble Detection Threshold.
Random NRDUCellPrach.R When many UEs are located beyond the

Access achAlgoOptSwitc cell radius, select the
Algorithm h CONTENTION_FREE_RA_OPT_SW option.
Opt Switch

Not involved

//Optimizing PRACH configurations
MOD NRDUCELLPRACH: NrDuCellId=0, CbraPreamblePct=255;
MOD NRDUCELL: NrDuCellId=0, PrachFreqStartPosition=65535;
//Optimizing the percentage by which the PRACH preamble detection threshold increases
MOD NRDUCELLPRACH: NrDuCellId=0, PrachThldIncreaseRate=0;
//Enabling non-contention-based RA optimization
MOD NRDUCELLPRACH: NrDuCellId=0, RachAlgoOptSwitch=CONTENTION_FREE_RA_OPT_SW-1;

Not involved


Step 1 Start Uu signaling tracing on the MAE-Access as follows: Log in to the MAE-Access
and choose Monitor > Signaling Trace > Signaling Trace Management. On the
displayed page, choose Trace Type > NR > Application Layer > Uu Interface
Trace.

(2020-01-20)
5G RAN
Step 2 Enable a UE to access the network. In SA networking, check the SIB1 tracing
result, as shown in Figure 7-6. Check the fields in the rach-ConfigCommon IE in
the SIB1. If the value of prach-ConfigurationIndex is the same as the configured
value, this function has taken effect.
In NSA networking, check the LTE message RRCConnectionReconfiguration. Check the same
IEs as described in SA networking.
Figure 7-6 SIB1 tracing report (SA networking)
----End

Observe the following counters to monitor RA:
● Contention-based RA: N.RA.Contention.Att, N.RA.Contention.Att.Max,
N.RA.Contention.Resp, N.RA.Contention.Msg3, and
N.RA.Contention.Resolution.Succ
● Non-contention-based RA: N.RA.Dedicated.Att, N.RA.Dedicated.Resp, and
N.RA.Dedicated.Msg3

(2020-01-20)
5G RAN
Description 8 CSI-RS Resource Management
8 CSI-RS Resource Management
8.1 Principles
CSI-RS in NR is classified into the following types:
● CSI-RS for CM: for downlink channel state measurements. In the current
version, the gNodeB sends CSI-RS for CM within the active BWP. UEs process
received CSI-RS for CM to obtain corresponding information such as the CQI,
RI, and PMI, and report the information to the gNodeB.
● CSI-RS for BM: for downlink beam measurements. In the current version, the
gNodeB sends CSI-RS for BM within the active BWP. UEs process received CSI-
RS for BM to obtain the corresponding reference signal received power
(RSRP), and report the RSRP and CSI-RS resource indicator (CRI) to the
gNodeB. The gNodeB then obtains the RSRP information about the
corresponding beam.
Only NR TDD, not NR FDD, allows for CSI-RS for BM.

● Tracking reference signal (TRS): In the current version, the gNodeB sends TRS
within the active BWP. UEs receive TRS for tracking time and frequency
offsets.
For more information on CSI-RS for CM, see "UE procedure for reporting channel state
information (CSI)" in 3GPP TS 38.214 (Release 15).
For more information on CSI-RS for BM, see "CSI-RS for L1-RSRP computation" in 3GPP TS
38.214 (Release 15).
For more information on TRS, see "CSI-RS for tracking" in 3GPP TS 38.214 (Release 15).
"CSI-RS" as mentioned in this section is not differentiated among CSI-RS for CM, CSI-RS for
BM, and TRS. If CSI-RS types need to be distinguished, CSI-RS for CM, CSI-RS for BM, or TRS
is used.
CSI-RS can be periodic CSI-RS, aperiodic CSI-RS, or semi-persistent CSI-RS.

(2020-01-20)
5G RAN
Table 8-1 Periodic CSI-RS, aperiodic CSI-RS, and semi-persistent CSI-RS

Type Description Support in This Version
Periodic The gNodeB ● In low frequency bands, CSI-RS for CM is

CSI-RS periodically sends periodically transmitted by default.
CSI-RS to UEs in The gNodeB periodically sends CSI-RS for CM
accordance with to UEs in accordance with the period
the configured specified by the NRDUCellCsirs.CsiPeriod
period. parameter and UEs send measurement
reports to the gNodeB. The number of
resources for periodic CSI-RS transmission is
specified by the
NRDUCellCsirs.CsirsCellResourceNum
parameter.
● In high frequency bands, CSI-RS for CM
cannot be periodically transmitted.
● TRS can be periodically transmitted.
The gNodeB periodically sends TRS to UEs in
accordance with the period specified by the
NRDUCellCsirs.TrsPeriod parameter.
● CSI-RS for BM can be periodically
transmitted.
Semi- After the MAC CE The current version does not support semi-
persisten is activated, the persistent CSI-RS.
t CSI-RS gNodeB
periodically sends
CSI-RS to UEs in
accordance with
the configured
period.
Aperiodic The gNodeB ● In low frequency bands, CSI-RS for CM can

CSI-RS sends DCI to UEs be aperiodically transmitted in specific
and sends CSI-RS scenarios.
to UEs in the slot ● In high frequency bands, CSI-RS for CM can
indicated in the be aperiodically transmitted.
DCI. UEs receive
CSI-RS from the ● TRS cannot be aperiodically transmitted.
gNodeB in the ● CSI-RS for BM cannot be aperiodically
indicated slot. transmitted.
CSI-RS measurement results are reported periodically or aperiodically. For details

about periodic reporting, see 6 PUCCH Channel Management. For details about
aperiodic reporting, see Scheduling.

(2020-01-20)
5G RAN
8.2.1 Benefits
CSI-RS resource management enables CSI-RS resources to be properly used to
8.2.2 Impacts
Network Impacts
A shorter CSI-RS transmission period increases the accuracy of channel
measurements, and guarantees the performance of the features that depend on
CSI-RS measurements. However, it also increases CSI-RS resource consumption.
A longer CSI-RS transmission period results in less CSI-RS resource consumption.
However, it also decreases the accuracy of channel measurements and results in
performance deterioration of the features that depend on CSI-RS measurements.
If a large number of UEs are served, UEs with high rate requirements are
preferentially allocated CSI-RS resources, and preempt CSI-RS resources of the UEs
that have low rate requirements when CSI-RS resources are insufficient. This
mechanism increases the possibility of service drops for UEs with low rate
requirements.
Function Impacts
Function Function Switch Refere Description
Name nce
High-speed NRDUCell.HighSpeed High High-speed cells (for which

Railway Flag Speed NRDUCell.HighSpeedFlag is
Superior Mobilit set to HIGH_SPEED) do not
Experience y support TRS periods longer
than 20 ms. This prevents
delayed tracking of time and
frequency offsets when UEs
are moving at high speeds.
DL CoMP INTRA_GNB_DL_JT_S CoMP For a cell enabled with DL

W option of the CoMP, throughput decreases
NRDUCellAlgoSwitch. for CoMP UEs when periodic
CompSwitch CSI-RS for CM is enabled and
parameter the value of the
NRDUCellCsirs.CsiPeriod
parameter is equal to 5 ms.

(2020-01-20)
5G RAN
Function Function Switch Refere Description

Name nce
Hyper Cell NRDUCell.NrDuCellN Hyper TRS is configured for the

etworkingMode Cell TRPs in a hyper cell in a
staggered manner to prevent
mutual interference based on
the different results of TRP ID
mod 6. CSI-RS for CM is
configured in the same
manner as that before TRP
combination.
DRX BASIC_DRX_SW option DRX ● Periodic CSI-RS for CM:

of the The gNodeB does not
NRDUCellUePwrSav- check CSI-RS
ing.NrDuCellDrxAlgoS measurement reports from
witch parameter UEs in DRX-defined sleep
time. As a result, the
number of valid CSI-RS
measurement reports
received by the gNodeB
decreases.
● Aperiodic CSI-RS for CM:
CSI-RS measurement
reports from UEs are sent
on the PUSCH, which may
cause continuous uplink
data scheduling for UEs.
As a result, the UEs cannot
enter the DRX-defined
sleep state.
8.3 Requirements
8.3.1 Licenses
8.3.2 Software
None

None

(2020-01-20)
5G RAN
8.3.3 Hardware
Base Station Models

Boards
RF Modules
8.3.4 Others
None

This function takes effect by default and no parameters are used for activation.
Table 8-2 describes the parameters used for function optimization.

Name
CSI Period NRDUCellCsirs.Cs It is recommended that the default value

iPeriod be retained.
This parameter takes effect only on CSI-RS
for CM in low frequency bands. This
function is irrelevant to high frequency
bands.
TRS Period NRDUCellCsirs.Tr It is recommended that the default value

sPeriod be retained.

(2020-01-20)
5G RAN

Name
CSIRS Cell NRDUCellCsirs.Cs It is recommended that the default value

Resource irsCellResource- be retained.
Number Num This parameter takes effect only on CSI-RS
for CM in low frequency bands. This
bands.

Not involved

//Configuring the period of periodic CSI-RS for CM transmission
MOD NRDUCellCSIRS: NrDuCellId=0, CsiPeriod=SLOT40;
//Configuring the period of periodic TRS transmission
MOD NRDUCellCSIRS: NrDuCellId=0, TrsPeriod=MS20;
//Configuring the number of resources for periodic CSI-RS for CM transmission
MOD NRDUCellCSIRS: NrDuCellId=0, CsirsCellResourceNum=4_RESOURCE;

Not involved


Step 1 Start Uu signaling tracing for the cell enabled with periodic CSI-RS measurements
as follows: Log in to the MAE-Access and choose Monitor > Signaling Trace >
Signaling Trace Management. On the displayed page, choose Trace Type > NR >
Application Layer > Uu Interface Trace.
Step 2 In SA networking, check the traced RRCReconfiguration message, as shown in
Figure 8-1. If each resource field in the csi-MeasConfig IE contains the value of
periodicityAndOffset, periodic CSI-RS measurements have taken effect.

(2020-01-20)
5G RAN
----End

None

(2020-01-20)
5G RAN
Description 9 SRS Resource Management
9 SRS Resource Management
9.1 Principles
9.1.1 Overview
SRS refers to uplink sounding signals. In the current version, UEs send SRS within
the active BWP. The gNodeB processes received SRS to obtain corresponding
information such as the signal to interference plus noise ratio (SINR), RSRP, and
PMI. The value of usage in SRS resource configurations determines which
functions SRS is used for (In the current version, usage can be set to codebook or
antennaSwitching in NR TDD, and only to codebook in NR FDD). Table 9-1
provides more details.
Table 9-1 Functions that SRS is used for

Value of Function Description
usage
codeboo Uplink single-user ● UEs perform PMI-based weighting

k multiple-input multiple- on data to be transmitted.
output (SU-MIMO)/multi- ● The gNodeB performs uplink SRS-
user multiple-input based link adaptation (LA) and
multiple-output (MU- sends the result to UEs to instruct
MIMO) them in data transmission.
Uplink beam The optimal receive beams are selected

management based on SRS to serve uplink channels.
Uplink timing For details, see 5G Networking and

Signaling.

(2020-01-20)
5G RAN
Value of Function Description

usage
antenna Downlink SU-MIMO/MU- ● In low frequency bands, the gNodeB

Switchin MIMO performs SRS weight-based
g weighting on data to be transmitted.
This function is irrelevant to high
frequency bands.
● The gNodeB performs downlink SRS-
based LA and sends data based on
the LA result.
Downlink beam In low frequency bands, the optimal

management transmit beams are selected based on
SRS to serve downlink channels. This
bands.
SRS is classified into three types: periodic SRS, semi-persistent SRS, and aperiodic
SRS.
● Periodic SRS
After resource configurations for periodic SRS are received, UEs periodically
send SRS.
The period of periodic SRS transmission can either be statically or dynamically
configured.
– If the SRS_PERIOD_ADAPT_SW option of the
NRDUCellSrs.SrsAlgoSwitch parameter is selected, the gNodeB
dynamically adjusts the SRS period based on SRS resource usage. The
SRS_PERIOD_ADAPT_SW option is selected for low-speed cells and
deselected for high-speed cells and hyper cells by default.
▪ When the number of UEs is small (for example, the

N.User.RRCConn.Avg counter returns a value less than 26 for 2T4R
UEs) and SRS resources are sufficient, a shorter SRS period improves
UE performance and cell performance.
▪ When the number of UEs is large (for example, the

N.User.RRCConn.Avg counter returns a value greater than 26 for
2T4R UEs) and SRS resources are insufficient, a longer SRS period
improves cell performance.
– If the SRS_PERIOD_ADAPT_SW option of the
NRDUCellSrs.SrsAlgoSwitch parameter is deselected, the SRS period is
specified by the NRDUCellSrs.SrsPeriod parameter.
● Semi-persistent SRS
After resource configurations for semi-persistent SRS are received, UEs
periodically send SRS only when the MAC CE is activated.
● Aperiodic SRS
After resource configurations for aperiodic SRS are received, UEs send SRS
according to the DCI for downlink scheduling.

(2020-01-20)
5G RAN
In low-frequency scenarios, the periodic mode is used.In high-frequency scenarios,

the aperiodic mode is used.
The SRS resources of each UE include multiple SRS sets. For more information on
the SRS resource parameters included in each SRS set, see section 6.3.2 "Radio
resource control information elements" in 3GPP TS 38.331 (Release 15).
SRS-related concepts are denoted as follows:
● SRS slot period: indicates the SRS transmission period for a UE. If a UE sends
SRS at an interval of X slots (or ms), X is the SRS slot period.
● SRS slot offset: indicates the time-domain positions (slot number) for SRS
transmission in each period.
For more information on these concepts, see section 6.2.1 "UE sounding
procedure" in 3GPP TS 38.214 (Release 15).
SRS resource configurations are signaled to UEs by the SRS-Config IE in an RRC

signaling message. After resource configurations for periodic SRS are received, UEs
periodically send SRS using the indicated time-frequency resources. After resource
configurations for aperiodic SRS are received, UEs send SRS using the scheduled
resources indicated in the DCI.
9.1.2 Cell-specific SRS

A cell-specific SRS slot includes the time-domain resources for all UEs in a cell to
transmit SRS. In NR, the gNodeB obtains the number and positions of slots
available for SRS transmissions in a radio frame and the number and positions of
symbols for SRS in the SRS slots based on slot assignment.
In NR TDD mode, SRS is only configured in the self-contained slots in a radio frame. In NR
FDD mode, SRS is only configured in the uplink-only slots in a radio frame.
For more information on the principles and configurations of slot assignment, see
Standards Compliance.
9.1.3 UE-specific SRS
9.1.3.1 UE-specific SRS Slot

A UE sends SRS in a UE-specific SRS slot. SRS slots are configured only for periodic
SRS and semi-persistent SRS, not for aperiodic SRS. The slots for aperiodic SRS are
determined during scheduling.
9.1.3.2 UE-specific SRS Bandwidth

NR allows UE-specific SRS bandwidths to be configured. A UE sends SRS using a
UE-specific SRS bandwidth. Specifications define a maximum of four types of SRS
bandwidths (BSRS = 0, 1, 2, or 3 in the SRS bandwidth configurations). Table 9-2
describes a UE-specific SRS bandwidth configuration example. For more
information, see section 6.4.1.4 "Sounding reference signal" in 3GPP TS 38.211.

(2020-01-20)
5G RAN
Table 9-2 UE-specific SRS bandwidth configurations
CSRS BSRS = 0 BSRS = 1 BSRS = 2 BSRS = 3
mSRS,0 N0 mSRS,1 N1 mSRS,2 N2 mSRS,3 N3
0 4 1 4 1 4 1 4 1
... ... ... ... ... ... ... ... ...
9 32 1 16 2 8 2 4 2
... ... ... ... ... ... ... ... ...
63 272 1 16 17 8 2 4 2
● CSRS: indicates the SRS bandwidth index.

● BSRS: indicates the bandwidth tree level.
● mSRS,B: indicates the SRS bandwidth on a BSRS level.
● NB: indicates the number of leaf nodes on a BSRS level.
● When BSRS is not 0, NB is calculated as follows: SRS bandwidth corresponding to
BSRS minus 1/SRS bandwidth corresponding to BSRS.
● When BSRS is 0, NB is 1.
Figure 9-1 shows an SRS bandwidth configuration tree corresponding to CSRS of 9,

where a UE-specific SRS bandwidth can be 32, 16, 8, or 4 RBs.
Figure 9-1 SRS bandwidth configuration tree
For aperiodic SRS, the system determines CSRS and BSRS for SRS bandwidths based
on the BWP.
The system separately determines CSRS and BSRS for broadband bandwidths and
narrowband bandwidths of periodic SRS based on the BWP. To improve SRS
measurement accuracy and coverage capability, SRS bandwidths for UEs are
dynamically adjusted based on the channel quality.
9.1.4 SRS Multiplexing

An SRS multiplexing mode determines how different UEs transmit SRS using time-
frequency resources. In NR, frequency division multiplexing (FDM) and code
division multiplexing (CDM) are applied.

(2020-01-20)
5G RAN
FDM
The FDM mode allows different UEs to transmit SRS using different frequencies.
There are two types of FDM: localized-FDM (L-FDM) and distributed-FDM (D-
FDM).
● L-FDM
Different UEs use different continuous frequency-domain resources to send
SRS.
● D-FDM
Different UEs alternately send SRS over subcarriers. In the current version, the
number of supported combs is 2, indicating that a bandwidth is divided into
even and odd subcarriers. For example, one UE sends SRS on odd subcarriers,
and another sends on even subcarriers. In this way, SRS transmissions are
staggered in the frequency domain. Also, the SRS transmission period for a
single UE is combed in the frequency domain, also known as D-FDM combing.
Figure 9-2 shows D-FDM combing. comb0 indicates the subcarriers used to
transmit SRS of one UE, and comb1 indicates the subcarriers used to transmit
SRS of another UE.
Figure 9-2 D-FDM combing
CDM
CDM allows SRS with the same symbol position, bandwidth, and comb (for
example, the SRS corresponding to two ports on a 2T4R UE) to occupy the same
time-frequency position. Codewords use cyclic shift sequences generated from the
same ZC sequence. In the current version, CDM allows for a maximum of four
cyclic shifts.
9.1.5 SRS Frequency Hopping

SRS frequency hopping enables a UE to transmit SRS on a small bandwidth in one
symbol and to transmit SRS on another bandwidth in the next symbol. In this way,
channel sounding is realized across the entire system bandwidth. Frequency
hopping offers channel quality measurements across the entire bandwidth using a
small sounding bandwidth. This version only supports intra-slot frequency hopping
for aperiodic SRS and inter-slot frequency hopping for periodic SRS.
9.2.1 Benefits
SRS resource management enables SRS resources to be properly used to improve
network performance.

(2020-01-20)
5G RAN
9.2.2 Impacts
Network Impacts
Enabling the SRS period adaptation function by selecting the
SRS_PERIOD_ADAPT_SW option of the NRDUCellSrs.SrsAlgoSwitch parameter
causes the cell to reset and all UEs served by the cell to re-access the network.
After the cell is reset, the initial SRS period of the cell is so large that all UEs in the
cell are allocated SRS resources. The time-to-trigger for each SRS period change in
the cell enabled with this function is 10 minutes. This mechanism prevents SRS
period changes from causing repeated signaling reconfiguration over the air
interface in the case of significant changes in the number of UEs.
After the SRS period adaptation function is enabled, the impacts on UEs in
different scenarios are as follows:
● When SRS resources are lightly loaded or at normal load, the gNodeB
separately configures shorter SRS periods for newly admitted UEs in a cell.
This reduces the SRS measurement interval and therefore better experience is
provided for such UEs but the SRS capacity of the cell is lowered.
In the case of small inter-site distances or strong inter-cell interference, for
example, for cell edge users (CEUs), a short SRS period increases inter-cell SRS
interference, affecting uplink and downlink user-perceived rates and cell
throughput.
If the difference between the measured SRS RSRP of the serving cell and that of a
neighboring cell is 3 dB, the UE is considered a CEU.
● When SRS resources are lightly loaded, the gNodeB prolongs SRS periods for
newly admitted UEs in a cell when allocating SRS resources. This allows more
UEs to access the cell but may degrade user experience.
● When SRS resources are seriously or extremely loaded, the gNodeB separately
configures longer SRS periods for newly admitted UEs in a cell. This allows
more UEs to access the cell and achieves a tradeoff between cell capacity and
performance.
A long SRS period affects the downlink experienced rates of users moving at a
speed of 30 km/h.
If SRS period adaptation is disabled by deselecting the SRS_PERIOD_ADAPT_SW
option of the NRDUCellSrs.SrsAlgoSwitch parameter, the gNodeB always uses
the SRS period specified by the NRDUCellSrs.SrsPeriod parameter.
● A smaller value of this parameter increases the accuracy of channel
measurements and guarantees the performance of the features that depend
on SRS measurements. However, it also results in more SRS resource
consumption and fewer online UEs transmitting SRS. As a result, the number
of UEs transmitting SRS in a cell may not reach the maximum.
● A larger value of this parameter results in less SRS resource consumption and
more online UEs transmitting SRS. However, it also decreases the accuracy of
channel measurements and causes the deterioration of performance of the
features that depend on SRS measurements.
● If the gNodeB always uses the SRS period, the number of UEs transmitting
SRS and cell performance may be difficult to reach a balance. The number of

(2020-01-20)
5G RAN
online UEs transmitting SRS is limited, and the cell throughput may decrease
when the number of UEs increases. Therefore, it is recommended that SRS
period adaptation be enabled by selecting the SRS_PERIOD_ADAPT_SW
option of the NRDUCellSrs.SrsAlgoSwitch parameter.
Function Impacts
Name
High-speed NRDUCell.HighSpeed High Speed In high-speed scenarios,

Railway Flag Mobility UEs move rapidly. A long
Superior SRS period adversely
Experience affects UE performance.
DRX BASIC_DRX_SW option DRX ● Periodic SRS: The

of the gNodeB does not
NRDUCellUePwrSav- check SRS from UEs
ing.NrDuCellDrxAlgoS in DRX-defined sleep
witch parameter time. Therefore, the
quantity of valid SRS
received by the
gNodeB decreases.
● Aperiodic SRS: SRS
measurement reports
from UEs are sent on
the PUSCH, which
may cause
continuous uplink
data scheduling for
UEs. As a result, the
UEs cannot enter the
DRX-defined sleep
state.
Intra-band NRDUCellAlgoSwitch. Carrier When intra-band CA is

CA CaAlgoSwitch Aggregation enabled and the SRS
period for a UE
supporting antenna
selection in a PCell
(which works on the
primary component
carrier) is 5 ms or 10
ms, SRS resources in an
SCell (which works on
the secondary
component carrier) may
fail to be allocated,
affecting user
experience.

(2020-01-20)
5G RAN
9.3 Requirements
9.3.1 Licenses
9.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
None

Name
High-speed NRDUCell.HighSpeed High Speed High-speed Railway

Railway Flag Mobility Superior Experience and
Superior SRS period adaptation
Experience are mutually exclusive.
9.3.3 Hardware
Base Station Models
Boards
RF Modules

(2020-01-20)
5G RAN
9.3.4 Others
None

This function takes effect by default and no parameters are used for activation.
Table 9-3 describes the parameters used for function optimization.

Name
SRS Algorithm NRDUCellSrs.SrsAlgoS This is a high-risk parameter.

Switch witch Changing the value of this
parameter will cause the cell to
automatically restart.
The SRS_PERIOD_ADAPT_SW
option of this parameter specifies
whether to enable SRS period
adaptation. It is recommended that
the default value be retained.
SRS Period NRDUCellSrs.SrsPerio Set this parameter to its

d recommended value. (This
parameter needs to be configured
only when SRS period adaptation is
disabled.)
If a short SRS period is configured,
the number of UEs transmitting SRS
in a cell may not reach the
maximum. If a long SRS period is
configured, the number of UEs
transmitting SRS in a cell increases,
but the performance of the features
that depend on SRS measurements
deteriorates.

N/A

(2020-01-20)
5G RAN

//Disabling SRS period adaptation
MOD NRDUCELLSRS: NrDuCellId=0, SrsAlgoSwitch=SRS_PERIOD_ADAPT_SW-0;
//Modifying the SRS period (This operation is required only when SRS period adaptation is disabled.)
MOD NRDUCELLSRS: NrDuCellId=0, SrsPeriod=SL160;

N/A


After SRS period adaptation is enabled, perform the following operations to check
if this function has taken effect:
Step 1 Start Uu signaling tracing for the cell enabled with SRS period adaptation as
follows: Log in to the MAE-Access and choose Monitor > Signaling Trace >
Signaling Trace Management. On the displayed page, choose Trace Type > NR >
Application Layer > Uu Interface Trace.
Step 2 In SA networking, check the traced RRCReconfiguration message, as shown in
Figure 9-3. If the value of periodicityAndOffset-p sl80 in the srs-Config IE varies
with different SRS periods, this function has taken effect.

(2020-01-20)
5G RAN
----End


(2020-01-20)
5G RAN
Description 10 Parameters
10 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

(2020-01-20)
5G RAN
Description 11 Counters
11 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All counters related to the feature are displayed.
----End

(2020-01-20)
5G RAN
Description 12 Glossary
12 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

(2020-01-20)
5G RAN
Description 13 Reference Documents
13 Reference Documents
● 3GPP TS 38.212: "NR; Multiplexing and channel coding"

● 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
● 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception"
● 3GPP TS 38.211: "NR; Physical channels and modulation"
● 3GPP TS 38.213: "NR; Physical layer procedures for control"
● 3GPP TS 38.214: "NR; Physical layer procedures for data"
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Scheduling
● Standards Compliance
● 5G Networking and Signaling
● Beam Management
● mmWave Beam Management
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation

(2020-01-20)

Channel Management (5G RAN3.1 - Draft A) PDF

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

Channel Management (5G RAN3.1 - Draft A) PDF

Uploaded by

Copyright:

Available Formats

5G RAN

Channel Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................5

5 PDCCH Channel Management........................................................................................... 21

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

6 PUCCH Channel Management........................................................................................... 30

7 PRACH Channel Management........................................................................................... 48

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

8 CSI-RS Resource Management........................................................................................... 61

9 SRS Resource Management................................................................................................ 68

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

Issue Draft A Copyright © Huawei Technologies Co., Ltd. v

This section describes changes not included in the "Parameters", "Counters",

1.1 5G RAN3.1 Draft A (2020-01-20)

Added support for Added the ● 3900 and 5900

Added PDCCH initial Added the ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

Change Description Parameter Change Base Station Model

Added support for Added the ● 3900 and 5900

Added support for Added the 3900 and 5900 series

Added support for Added the ● 3900 and 5900

Added support for Added the following ● 3900 and 5900

Added support for Added the ● 3900 and 5900

Added support for Added the ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter Change Base Station Model

Modified the CSI ● Added the ● 3900 and 5900

Added support for Added the ● 3900 and 5900

Modified the default None ● 3900 and 5900

Optimized non- Added the ● 3900 and 5900

Added support for 120 None 3900 and 5900 series

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Change Base Station Model

Added support for PRACH None ● 3900 and 5900

Added support fot an Added the ● 3900 and 5900

Changed the name of None ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

2 About This Document

2.1 General Statements

2.2 Features in This Document

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

Feature Feature Name Section

FBFD-01 Channel Management 4 PBCH Channel

2.3 Differences Between NR FDD and NR TDD

Physical broadcast This function is supported by both 4 PBCH Channel

Physical downlink This function is supported by both 5 PDCCH Channel

Physical uplink None 6 PUCCH Channel

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

Function Name Difference Section

Physical random This function is supported by both 7 PRACH Channel

Channel state This function is supported by both 8 CSI-RS Resource

Sounding reference This function is supported by both 9 SRS Resource

2.4 Differences Between NSA and SA

PBCH channel None 4 PBCH Channel

PDCCH channel None 5 PDCCH Channel

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

Function Name Difference Section

PUCCH channel None 6 PUCCH Channel

PRACH channel None 7 PRACH Channel