5G RAN3.1 Basic Feature Description

5G RAN3.
1 Basic Feature Description
5G RAN3.1 Basic Feature Description
Issue 01
Date 2020-05-08
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 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. i

5G RAN3.1 Basic Feature Description Contents
Contents
1 Change History .............................................................................................................................. 1

2 Standards Compliance ................................................................................................................. 3
2.1 FBFD-010001 3GPP R15 Standards Compliance ........................................................................................................ 3
2.2 FBFD-010002 LDPC+Polar Codes .............................................................................................................................. 4
2.3 FBFD-010003 MIMO Basic Package ........................................................................................................................... 5
2.4 FBFD-010004 Basic Numerology ................................................................................................................................ 7
2.5 FBFD-010005 Self-contained Frame Structure ............................................................................................................ 8
2.6 FBFD-020100 Slot Configuration ................................................................................................................................ 9
2.7 FBFD-010006 F-OFDM ............................................................................................................................................. 11
2.8 FBFD-030101 NR FDD (Non Massive MIMO) ......................................................................................................... 12
3 RAN Architecture & Features ................................................................................................... 15

3.1 FBFD-010007 Scalable Bandwidth ............................................................................................................................ 15
3.2 FBFD-010008 Basic Modulation Schemes ................................................................................................................ 17
3.3 FBFD-010009 Channel Management ......................................................................................................................... 18
3.3.1 Logical Channel Management ................................................................................................................................. 19
3.3.2 Transport Channel Management .............................................................................................................................. 20
3.3.3 Physical Channel Management ................................................................................................................................ 21
3.3.4 Basic Performance of Uplink Control Channels ...................................................................................................... 22
3.3.5 Basic Performance of Downlink Control Channels ................................................................................................. 23
3.3.6 Uplink Timing Basic Performance........................................................................................................................... 24
3.3.7 SRS Basic Performance ........................................................................................................................................... 24
3.3.8 Random Access ........................................................................................................................................................ 25
3.4 FBFD-010010 Power Control ..................................................................................................................................... 26
3.4.1 PRACH Power Control ............................................................................................................................................ 27
3.4.2 PUSCH Power Control ............................................................................................................................................ 28
3.4.3 PUCCH Power Control ............................................................................................................................................ 28
3.4.4 SRS Power Control .................................................................................................................................................. 29
3.4.5 PBCH Power Control .............................................................................................................................................. 29
3.4.6 SS Power Control .................................................................................................................................................... 29
3.4.7 PDCCH Power Control ............................................................................................................................................ 30
3.4.8 TRS Power Control .................................................................................................................................................. 30
3.4.9 PDSCH Power Control ............................................................................................................................................ 30
Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. ii

3.5 FBFD-010011 Scheduling .......................................................................................................................................... 30

3.5.1 Uplink Non-Consecutive Scheduling ...................................................................................................................... 31
3.5.2 Enhanced Adaptive Retransmission ......................................................................................................................... 32
3.6 FBFD-010013 Radio Interface Ciphering................................................................................................................... 32
3.7 FBFD-010014 Mobility Management ........................................................................................................................ 33
3.7.1 Basic Functions for Mobility Management ............................................................................................................. 34
3.7.2 Intra-NR Coverage-based Intra-Frequency Handover ............................................................................................. 34
3.7.3 Intra-NR Coverage-based Inter-Frequency Handover ............................................................................................. 35
3.7.4 Intra-NR Frequency-Priority-based Inter-Frequency Handover .............................................................................. 36
3.7.5 Multi-Band Compatibility........................................................................................................................................ 36
3.8 FBFD-010015 Basic Beam Management ................................................................................................................... 37
3.9 FBFD-020101 Reliability ........................................................................................................................................... 38
3.9.1 Flow Control ............................................................................................................................................................ 39
3.9.2 Cell Outage Detection .............................................................................................................................................. 40
3.9.3 Base Station Always Online..................................................................................................................................... 41
3.9.4 Cold Backup of Main Control Boards ..................................................................................................................... 41
3.9.5 Inter-Board Baseband Resource Redundancy .......................................................................................................... 42
3.10 FBFD-020102 Radio QoS Management ................................................................................................................... 42
3.11 FBFD-021102 Integrity Protection ........................................................................................................................... 43
3.12 FBFD-021103 DRX .................................................................................................................................................. 45
3.13 FBFD-021104 SA Option 2 Architecture .................................................................................................................. 46
3.14 FBFD-031102 Inactive State .................................................................................................................................... 47
4 Transmission & Security ........................................................................................................... 50

4.1 FBFD-010016 Transmission Networking ................................................................................................................... 50
4.1.1 Star Topology ........................................................................................................................................................... 51
4.1.2 Chain Topology........................................................................................................................................................ 52
4.1.3 Tree Topology .......................................................................................................................................................... 52
4.2 FBFD-010017 CPRI Compression ............................................................................................................................. 53
4.3 FBFD-010018 Basic QoS Management ..................................................................................................................... 54
4.4 FBFD-010019 VLAN Support (IEEE802.1p/q) ......................................................................................................... 56
4.5 FBFD-010020 Synchronization .................................................................................................................................. 57
4.5.1 Clock Source Switching Manually or Automatically............................................................................................... 58
4.5.2 Synchronization with GPS ....................................................................................................................................... 58
4.5.3 Synchronization with BeiDou .................................................................................................................................. 59
4.5.4 Synchronization with Galileo .................................................................................................................................. 60
4.5.5 Synchronization with 1PPS+TOD ........................................................................................................................... 61
4.5.6 BITS Clock Synchronization ................................................................................................................................... 62
4.5.7 E1/T1 Clock Synchronization .................................................................................................................................. 62
4.5.8 Clock Out-of-Synchronization Detection ................................................................................................................ 63
4.5.9 Network-wide Synchronization Deviation Detection .............................................................................................. 63
4.6 FBFD-010022 Active/Standby IP Routes ................................................................................................................... 64
Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. iii

4.7 FBFD-010023 Security Mechanism ........................................................................................................................... 65

4.7.1 PKI ........................................................................................................................................................................... 66
4.7.2 gNodeB Supporting PKI Redundancy ..................................................................................................................... 66
4.7.3 Integrated Firewall ................................................................................................................................................... 67
4.7.4 Access Control Based on 802.1X............................................................................................................................. 67
4.7.5 DTLS over SCTP ..................................................................................................................................................... 67
4.7.6 Anti-DDoS Attack over the Air Interface ................................................................................................................. 68
4.8 FBFD-010024 IP Performance Monitoring ................................................................................................................ 69
4.9 FBFD-021101 IPv4/IPv6 Dual Stack .......................................................................................................................... 70
4.10 FBFD-010025 Basic O&M Package ........................................................................................................................ 70
4.10.1 Centralized U2020 Management ........................................................................................................................... 71
4.10.2 Local Maintenance on the LMT ............................................................................................................................ 72
4.10.3 Software Version Upgrade Management ............................................................................................................... 72
4.10.4 Hot Patch Management .......................................................................................................................................... 73
4.10.5 License Management ............................................................................................................................................. 73
4.10.6 Emergency License Control ................................................................................................................................... 74
4.10.7 Fault Management ................................................................................................................................................. 74
4.10.8 Configuration Management ................................................................................................................................... 75
4.10.9 Performance Management ..................................................................................................................................... 75
4.10.10 Inventory Management ........................................................................................................................................ 76
4.10.11 Energy Consumption Management ...................................................................................................................... 77
4.11 FBFD-031003 PSU Shutdown .................................................................................................................................. 77
5 Acronyms and Abbreviations ................................................................................................... 79

6 Appendix ...................................................................................................................................... 87
6.1 Appendix 1: NR Spectrum List ................................................................................................................................... 87
Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. iv

5G RAN3.1 Basic Feature Description 1 Change History
1 Change History
Issue Date Author Description
Draft V1.2 2018-12-04 Liu Qian Updated the NR spectrum list in the
(employee appendix.
ID:
00450988)
Draft V1.2 2018-12-20 Liu Qian Added the description of sub-3 GHz 2.6
(employee GHz (TDD) to FBFD-010007 Scalable
ID: Bandwidth. Moved the description of
00450988) LampSite from "Dependency" to
"Description."
Draft V1.2 2018-12-20 Liu Qian Added the description that the EN-DC
(employee mobility requires the UE to support LTE
ID: and NR DC to "Dependency" of
00450988) FBFD-020102 Mobility Management.
Draft V1.2 2018-12-20 Liu Qian Added the description that UEs need to
(employee support DRX to "Dependency" of
ID: FBFD-021103 DRX.
00450988)
Draft V1.2 2019-01-10 Liu Qian Added the description of SA architecture
(employee to the star topology of FBFD-010016
ID: Transmission Networking.
00450988)
Draft V1.2 2019-01-10 Liu Qian Added the restriction on the bandwidth
(employee supported by the UBBPfw1 board to
ID: FBFD-010007 Scalable Bandwidth.
00450988)
V1.1 2019-02-12 Liu Qian FBFD-010001 3GPP R15 Standards
(employee Compliance: Updated the 3GPP Release
ID: 15 version that 5G RAN2.1 complies
00450988) with to the version released in December
2018.
5G RAN3.0 2019-08-06 Tan Dongwei Added a new feature:
draft V1.0 (employee
Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 1

5G RAN3.1 Basic Feature Description 1 Change History
Issue Date Author Description

ID: FBFD-030101 NR FDD
00421350) Enhanced the following features:
FBFD-010014 Mobility Management:
Added support for intra-NR
inter-frequency handover
FBFD-021104 SA Option 2 Architecture:
Added support for NG-flex
FBFD-010020 Synchronization: Added
support for clock out-of-synchronization
detection
FBFD-010023 Security Mechanism:
Added support for TLS1.3
FBFD-020100 Slot Configuration: Added
support for dual-period 8:2 slot
assignment, which lasts 5 ms
FBFD-020101 Reliability: Added support
for cell outage detection in two new
scenarios
5G RAN3.0 2019-11-05 Tan Dongwei 1. Changed the feature name from
V1.0 (employee FBFD-030101 NR FDD to NR FDD
ID: (Non Massive MIMO).
00421350) 2. Modified the description of
FBFD-010011 Scheduling based on
trouble ticket DTS2019101011079.
5G RAN3.0 2019-12-31 Tan Dongwei 1. Modified the description of MIMO
V1.1 (employee Basic Package, Basic Beam Management,
ID: and 3D Coverage Pattern based on
00421350) trouble ticket DTS2019120905709.
5G RAN3.1 2020-01-15 Tu Yu TR5
(employee
ID:
00300675)

5G RAN3.1 Basic Feature Description 2 Standards Compliance
2 Standards Compliance
2.1 FBFD-010001 3GPP R15 Standards Compliance

2.2 FBFD-010002 LDPC+Polar Codes
2.3 FBFD-010003 MIMO Basic Package
2.4 FBFD-010004 Basic Numerology
2.5 FBFD-010005 Self-contained Frame Structure
2.6 FBFD-020100 Slot Configuration
2.7 FBFD-010006 F-OFDM
2.8 FBFD-030101 NR FDD (Non Massive MIMO)
2.1 FBFD-010001 3GPP R15 Standards Compliance

Availability
This feature is available as of 5G RAN1.0.
Summary
Huawei 5G RAN3.1 gNodeBs comply with 3GPP Release 15 (released in June 2019).
Benefits
Compliance with 3GPP Release 15 of 5G NR helps to facilitate large-scale commercial use of
5G and reduce end to end (E2E) industry costs.
Description
Huawei is an active participant and a major contributor to the development of 3GPP
specifications. In addition, Huawei strictly complies with 3GPP specifications during product
development. Specifically, Huawei 5G gNodeBs comply with 3GPP Release 15.

Enhancement
Huawei 5G gNodeBs comply with 3GPP Release 15 (released in June 2019).
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
2.2 FBFD-010002 LDPC+Polar Codes

Availability
Summary
This feature provides new channel coding schemes over the 5G NR air interface.
Benefits
Compared with LTE, 5G introduces two new air interface coding technologies: Low-Density
Parity Check (LDPC) code and Polar code.
The LDPC code supports a higher peak rate, a faster decoding rate, and lower power
consumption than the Turbo code. This makes the LDPC code more suitable for data decoding
required by 5G large bandwidth and high throughput scenarios. When the signal-to-noise ratio
(SNR) reaches a certain threshold, the LDPC code performance continues to rapidly improve
with the increase of the SNR. However, the Turbo code performance only shows a slight
improvement.
The polar code supports a lower code rate, has a lower demodulation threshold, and features a
higher error correction performance than the LTE convolutional code. The downlink polar
code supports decoding early termination. These factors enable the polar code to have a
higher decoding speed than the LTE convolutional code.
Description
The LDPC code uses the parity check matrix and is applicable to data channel coding in
Enhanced Mobile Broadband (eMBB) scenarios.

The polar code uses the encoding matrix and is applicable to control channel coding in eMBB
scenarios.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
2.3 FBFD-010003 MIMO Basic Package

Availability
Summary
MIMO Basic Package allows 5G gNodeBs to use multiple antennas to transmit and receive
signals. Multiple antennas can form narrow beams and enable beams to precisely target UEs,
improving coverage performance.
 Sub-3 GHz indicates frequency bands below 3 GHz.

 Sub-6 GHz indicates frequency bands ranging from 3 GHz to 6 GHz. 3GPP defines the n77, n78,
and n79 bands as sub-6 GHz.
 mmWave indicates millimeter wave bands. 3GPP defines the n257, n258, n260, and n261 bands as
mmWave.
For details about the spectrum, see 3GPP TS 38.104.
Benefits
This feature improves system coverage and spectral efficiency.
Description
MIMO Basic Package increases the number of antennas at the transmitter and receiver. It also
provides signal processing functions including downlink beamforming and uplink

multi-antenna reception. This improves the communications system coverage without

increasing the bandwidth.
Downlink beamforming for sub-6 GHz uses the interference principle to form user-targeted
beams, thereby enhancing signal strength and quality.
 Channel calibration: The amplitude and phase differences exist between RF transmit and
receive channels. Such differences vary with transmit and receive channels. Channel
calibration is required to ensure the amplitude and phase consistency between RF
transmit and receive channels. The gNodeB calculates the variations of the phase,
amplitude, and delay of known calibration signals transferred over different transmit and
receive channels. Then, the gNodeB compensates the phase, amplitude, and delay for the
channels based on these calculations.
 Weight calculation: The gNodeB calculates a vector based on downlink channel
characteristics to adjust the shape and direction of beams. When a UE is located in the
cell center, channel estimation and weight calculation are performed based on sounding
reference signals (SRSs). When a UE is located at the cell edge and SRSs are unreliable,
channel estimation and PMI weight calculation are performed based on channel state
information-reference signals (CSI-RSs).
 Weighting: During weighting, the gNodeB uses the vector adding function to add the
calculated weight value and the data to be transmitted, including data streams and
demodulation reference signals (DMRSs). The width and direction of beams are adjusted
based on the calculations.
 Beamforming implementation: Beamforming uses the interference principle to form
user-targeted beams. The signal strength increases when two wave peaks intersect with
each other and decreases when a wave peak intersects with a wave bottom.
Uplink multi-antenna reception for sub-6 GHz: After a UE precodes and transmits data,
the gNodeB receives the data over multiple antennas. This technology enhances signal
reception by means of space diversity and coherent reception that provide diversity gains
and array gains, respectively.
The basic beamforming procedure for mmWave is the same as that for sub-6 GHz. The
difference lies in weight calculation. For mmWave, both analog and digital beamforming
are used. Analog beamforming is performed on the RF part and digital beamforming is
performed on the baseband part. The gNodeB selects an analog beam according to the
UE-reported beam ID, and calculates a vector for this analog beam based on downlink
channel characteristics, so as to obtain further beamforming gains. When a UE is in the
cell center, channel estimation and weight calculation are performed based on SRSs.
When a UE is at the cell edge and SRSs are unreliable, channel estimation and PMI
weight calculation are performed based on CSI-RSs.
Enhancement
None
Dependency
 Hardware
Sub-6 GHz 2T2R/4T4R/8T8R/32T32R/64T64R base stations support downlink
beamforming and uplink multiple-antenna reception.
Sub-6 GHz 2T2R base stations do not support channel calibration.
mmWave base stations support 2T2R and 4T4R.
 UE

None
 Core network
None
 Other NEs
None
 Other features
None
2.4 FBFD-010004 Basic Numerology

Availability
Summary
The flexible numerology in 3GPP Release 15 enables the selection of appropriate subcarrier
spacing and cyclic prefix (CP) length for diversified services (such as eMBB, URLLC, and
mMTC) and frequency bands (such as sub-3 GHz, sub-6 GHz, and mmWave).
The subcarrier spacing configurations supported in the current version are as follows:
15 kHz subcarrier spacing for sub-3 GHz
120 kHz subcarrier spacing for mmWave
Benefits
For sub-6 GHz frequency bands, small subcarrier spacing is used. Longer CP lengths better
resist multipath delay and fading, and bring higher coverage performance. For mmWave
frequency bands, large subcarrier spacing is used for improving the capability of resisting the
phase noise and helps enhance system performance.
Description
The following subcarrier spacing configurations are supported for data channels by 3GPP
Release 15: 15 kHz, 30 kHz, 60 kHz, and 120 kHz. Extended CPs are only supported when
the subcarrier spacing is 60 kHz. Other subcarrier spacing configurations only support normal
CPs.
The subcarrier spacing configurations applicable to Basic Numerology in the current version
are as follows:
120 kHz subcarrier spacing for mmWave

Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
2.5 FBFD-010005 Self-contained Frame Structure

Availability
Summary
Compared with a non-self-contained slot, a self-contained slot comprises uplink and downlink
parts. The downlink part is used for the transmission of physical downlink control channels
(PDCCHs) and physical downlink shared channels (PDSCHs), and the uplink part is used for
the transmission of SRSs and physical uplink control channels (PUCCHs).
Benefits
When the uplink part of a self-contained slot is used for transmitting SRSs, the chances of
transmitting SRSs are increased. In this case, certain downlink channel information can be
obtained in an effective and timely manner based on the reciprocity between uplink and
downlink channels in TDD mode.
The uplink part of a self-contained slot can be used for transmitting ACK/NACK information
(carried on the PUCCH), which shortens the delay in downlink feedback and uplink
scheduling and improves user experience.
Description
Self-contained slots are classified into DL-dominant slots and UL-dominant slots. The uplink
part of DL-dominant slots can be used for the transmission of uplink control signals and SRSs.
The downlink part of UL-dominant slots can be used for the transmission of downlink control
signals.
Currently, only DL-dominant slots are supported.

The white area in the preceding figure indicates the guard period (GP) between uplink and
downlink transmission.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
2.6 FBFD-020100 Slot Configuration

Availability
5G RAN1.0 supports the default slot configuration of 4:1.
5G RAN2.0 introduces a slot configuration of 8:2.
Summary
In a TDD system, uplink and downlink slot resources need to be configured based on a certain
ratio, which is also called slot configuration.
In addition to the default 2.5 ms single-period (4:1 DDDSU) configuration, the following
configurations are also supported:
5 ms single-period (8:2 DDDDDDDSUU)
5 ms dual-period (8:2 DDDSUUDDDD)
5 ms dual-period (7:3 DDDSUDDSUU)

The function of checking slot configurations and frame offsets is now supported. This
function enables users to identify and resolve the interference issues resulting from
inconsistent base station frame offsets and slot configurations between the local cell and
intra-frequency cells in the same area when sites are newly deployed, base station frame
offsets or cell slot configurations are modified, cells are added, or cells are deleted.
Benefits
This feature enables alignment with switching points between LTE TDD (with a slot
configuration of DDDSU and a subcarrier spacing configuration of 15 kHz) uplink and
downlink. The alignment mitigates the uplink and downlink interference between LTE and
NR.
Description
A 5 ms period includes 10 timeslots (the corresponding subcarrier spacing configuration is 30
kHz), as shown by slots 0 to 9 in the following figure.
In this figure, the orange part indicates the downlink, the blue part indicates the uplink, and
the white part indicates the guard period (GP) for the switch of uplink and downlink
transmission.
A 5 ms period includes 7 downlink timeslots, 2 uplink timeslots, and 1 self-contained timeslot
(S timeslot for short).
The following figure shows the allocation of self-contained timeslot resources. Four uplink
symbols are used for sounding reference signal (SRS) transmission. The number of GP
symbols can be configured and ranges from 1 to 6. Correspondingly, the number of downlink
symbols ranges from 9 to 4.
Enhancement
 5G RAN3.0
The function of checking slot configurations and frame offsets is introduced.
The dual-period 8:2 slot configuration and its corresponding slot structures are introduced.
Dependency
 Hardware
4:1: no dependency
8:2: not supported by the AAU5612
 UE
None
 Core network

None
 Other NEs
None
 Other features
None
2.7 FBFD-010006 F-OFDM

Availability
Summary
The F-OFDM feature enables 5G to achieve higher spectrum usage.
The spectral utilization refers to the ratio of transmission bandwidth to channel bandwidth.
Table 2-1 Maximum spectrum utilization of different sub-6 GHz channel bandwidths
Subcarrier Channel Bandwidth

Spacing
(kHz) 40 MHz 60 MHz 80 MHz 100 MHz
30 95.4% 97.2% 97.65% 98.28%
Table 2-2 Maximum spectrum utilization of different mmWave channel bandwidths

Subcarrier Spacing (kHz) Channel Bandwidth
100 MHz 200 MHz
120 95.04% 95.04%
Benefits
Compared with the 90% spectral utilization of LTE, F-OFDM enables higher spectrum
utilization for 5G and more spectrum resources within the channel bandwidth. When the 100
MHz channel bandwidth and 30 kHz subcarrier spacing are used, an additional 8.28 MHz of
spectrum resources can be used for 5G.
Description
On the gNodeB transmitter side, the F-OFDM feature effectively controls the out-of-band
leakage of transmit signals, reduces the guard band within the 5G channel bandwidth, and
enables more spectrum to be used for downlink transmission. On the gNodeB receiver side,
the F-OFDM feature effectively controls the impact of out-of-band interference on 5G,

reduces the guard band within the 5G channel bandwidth, and enables more spectrum to be
used for uplink transmission.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
2.8 FBFD-030101 NR FDD (Non Massive MIMO)

Availability
Summary
FDD is a full-duplex communications technology used in mobile communications, which is
different from TDD. In FDD, two independent channels are used for downlink transmission
and uplink transmission, respectively.
Benefits
This feature allows 5G to be deployed in more frequency bands based on the requirements
defined in 3GPP specifications. The sub-3 GHz FDD frequency band features low frequencies
and provides better coverage.
Description
In FDD, two independent channels are used for uplink transmission and downlink
transmission, respectively.
The subcarrier spacing is 15 kHz.
FDD can be deployed in the n1, n2, n3, n5, n7, n8, n20, n25, n28, n66, and n71 frequency
bands.
The cell bandwidths 5 MHz, 10 MHz, 15 MHz, and 20 MHz are supported.

Enhancement
Frequency bands n2, n5, n8, n20, and n25 are supported in 5G RAN3.1.
Dependency
 Hardware
Baseband processing unit: UBBPg
All 5000 series RF modules support NR FDD, except those working in the 1400 MHz
and 1900 MHz frequency bands. The 3000 series RF modules supporting NR FDD are
listed in the following table.
Module Frequency Band

RRU3971a 1.8/n3
RRU3971 2.1/n1, 1.8/n3, and AWS/n66
RRU3959w 1.8/n3
RRU3959a 2.1/n1, 1.8/n3, P900/n8, and E900/n8
RRU3959 2.1/n1, 1.8/n3, P900/n8, and E900/n8
RRU3958 2.1/n1
RRU3953w 1.8/n3
RRU3953 2.1/n1, 1.8/n3, P900/n8, and E900/n8
RRU3952m 2.1/n1 and 1.8/n3
RRU3952 2.1/n1 and 850/n5
RRU3930E 2.1/n1
RRU3832 AWS/n4 and AWS/n66
RRU3281 2.6/n7
RRU3269 700/n12+n13
RRU3262 2.6/n7, 850/n5, and 700/n28
RRU3230E 1.8/n3 and 2.6/n7
RRU3962 2.1/n1+1.8/n3
RRU3965/RRU3965d 800/n20+900/n8
AAU3940 2.1/n1+1.8/n3
 UE
UEs must support FDD in the corresponding frequency bands.
 Core network
None
 Other NEs

None
 Other features
None

5G RAN3.1 Basic Feature Description 3 RAN Architecture & Features
3 RAN Architecture & Features
3.1 FBFD-010007 Scalable Bandwidth

3.2 FBFD-010008 Basic Modulation Schemes
3.3 FBFD-010009 Channel Management
3.4 FBFD-010010 Power Control
3.5 FBFD-010011 Scheduling
3.6 FBFD-010013 Radio Interface Ciphering
3.7 FBFD-010014 Mobility Management
3.8 FBFD-010015 Basic Beam Management
3.9 FBFD-020101 Reliability
3.10 FBFD-020102 Radio QoS Management
3.11 FBFD-021102 Integrity Protection
3.12 FBFD-021103 DRX
3.13 FBFD-021104 SA Option 2 Architecture
3.14 FBFD-031102 Inactive State
3.1 FBFD-010007 Scalable Bandwidth

Availability
Summary
This feature allows for the following bandwidth configurations:
 Macro Base Stations
− Low frequency bands in NR TDD mode: 20 MHz, 30 MHz, 40 MHz, 50 MHz, 60
MHz, 70 MHz, 80 MHz, 90 MHz, and 100 MHz

− High frequency bands in NR TDD mode: 100 MHz and 200 MHz
− NR FDD: 5 MHz, 10 MHz, 15 MHz, and 20 MHz
 LampSite Base Stations
Low frequency bands in NR TDD mode: 20 MHz, 30 MHz, 40 MHz, 50 MHz, 60 MHz,
70 MHz, 80 MHz, 90 MHz, and 100 MHz
UE:
UEs can access cells served by bandwidth-scalable carriers of the gNodeB based on the
bandwidth part (BWP) protocol.
Benefits
With operators' spectrum fully utilized, this feature protects spectrum investment and ensures
that UEs with different bandwidth capabilities can access the 5G NR network.
Description
This feature allows for the following bandwidth configurations:
 Macro Base Stations
− Low frequency bands in NR TDD mode: 20 MHz, 30 MHz, 40 MHz, 50 MHz, 60
MHz, 70 MHz, 80 MHz, 90 MHz, and 100 MHz
− High frequency bands in NR TDD mode: 100 MHz and 200 MHz
− NR FDD: 5 MHz, 10 MHz, 15 MHz, and 20 MHz
 LampSite Base Stations
Low frequency bands in NR TDD mode: 20 MHz, 30 MHz, 40 MHz, 50 MHz, 60 MHz,
70 MHz, 80 MHz, 90 MHz, and 100 MHz
UE:
UEs can access cells served by bandwidth-scalable carriers of the gNodeB based on the
bandwidth part (BWP) protocol.
Enhancement
In 5G RAN2.0, this feature applies to the 4.8–5.0 GHz frequency range.
5G RAN2.1 adds support for 20 MHz, 30 MHz, 50 MHz, 70 MHz, and 90 MHz bandwidths
in 3.4–3.8 GHz frequency bands.
5G RAN2.1 adds support for 60 MHz, 80 MHz, and 100 MHz bandwidths in TDD 2.6 GHz
frequency bands.
Dependency
 Hardware
RF module: support for nTnR but not massive MIMO
700 MHz (n28):
RRU5309, RRU5909, RRU5509t, and RRU5301cw
1800 MHz (n3):
RRU5901, RRU5904, RRU3959, RRU3953, and RRU3971

2100 MHz (n1):

RRU5909 and RRU3959
n3+n1:
RRU5508, RRU5502, and RRU5505
Baseband processing unit: The UBBPg2a and UBBPg3 support all bandwidth
configurations. The UBBPfw1 supports only 40 MHz, 60 MHz, 80 MHz, and 100 MHz.
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.2 FBFD-010008 Basic Modulation Schemes

Availability
Summary
Modulation schemes supported in 5G RAN1.0 include UL π/2-BPSK, DL/UL QPSK, DL/UL
16QAM, and DL/UL 64QAM.
Benefits
Spectral efficiency and system capacity are maximized by selecting modulation schemes in
line with channel conditions.
Description
Modulation schemes are selected to adapt to UE-reported CQIs, maximizing system
throughput for UEs.
This feature provides the gNodeB and UEs with the following modulation schemes:
 Quadrature phase shift keying (QPSK) in the uplink and downlink
 16 quadrature amplitude modulation (16QAM) in the uplink and downlink
 64QAM in the uplink and downlink
In modulation with QPSK, 16QAM, and 64QAM:
 QPSK carries two bits at most per symbol.
 16QAM carries four bits at most per symbol.
 64QAM carries six bits at most per symbol.

Based on channel conditions, the gNodeB and UEs select the most suitable modulation
scheme to balance data transmission rates and frame error rates.
A more favorable channel condition allows a higher-order modulation scheme to be used.
For example, in poor radio environments, UEs use a low-order modulation scheme (QPSK) to
ensure that uplink transmission meets service requirements. In good radio environments, UEs
use a high-order modulation (for example, 64QAM) to realize high-rate transmission in the
uplink.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.3 FBFD-010009 Channel Management

Availability
Summary
This feature covers logical channels, transport channels, physical channels, and other basic
functions. It provides the basis for UEs to access an NR system and transmit data.
Benefits
This feature provides the basis for data transfer and resource management.
Enhancement
None
Dependency
 Hardware

None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.3.1 Logical Channel Management

Description
Logical channels connect the Media Access Control (MAC) layer and the Radio Link Control
(RLC) layer. Logical channels are classified into control channels and traffic channels based
on the type of transmitted data.
Control channels include:
 Broadcast control channel (BCCH)
 Paging control channel (PCCH)
 Common control channel (CCCH)
 Dedicated control channel (DCCH)
Traffic channels include:
Dedicated traffic channel (DTCH)
The mapping between logical channels and transport channels is as follows:
1. Uplink
 The CCCH is mapped to the uplink shared channel (UL-SCH).
 The DCCH is mapped to the UL-SCH.
 The DTCH is mapped to the UL-SCH.
Table 3-1 describes the mapping between uplink logical channels and uplink transport
channels.
Table 3-1 Mapping between uplink logical channels and uplink transport channels
Transport Channel UL-SCH Random Access Channel
Logical Channel (RACH)
CCCH X
DCCH X
DTCH X
2. Downlink

 The BCCH is mapped to the broadcast channel (BCH).

 The BCCH is mapped to the downlink shared channel (DL-SCH).
 The PCCH is mapped to the paging channel (PCH).
 The CCCH is mapped to the DL-SCH.
 The DCCH is mapped to the DL-SCH.
 The DTCH is mapped to the DL-SCH.
Table 3-2 describes the mapping between downlink logical channels and downlink transport
channels.
Table 3-2 Mapping between downlink logical channels and downlink transport channels
Transport Channel BCH PCH DL-SCH
Logical Channel
BCCH X X
PCCH X
CCCH X
DCCH X
DTCH X
Benefits
3.3.2 Transport Channel Management

Description
Transport channels connect the MAC layer and the physical layer. Transport channels are
classified based on the type of transmitted data and the method of data transmission over the
air interface.
Downlink transport channels include:
 BCH
 DL-SCH
 PCH
Uplink transport channels include:
 UL-SCH
 RACH
The mapping between transport channels and physical channels is as follows:
1. Uplink
 The UL-SCH is mapped to the physical uplink shared channel (PUSCH).

 The RACH is mapped to the physical random access channel (PRACH).

Figure 3-1 shows the mapping between uplink transport channels and uplink physical
channels.
Figure 3-1 Mapping between uplink transport channels and uplink physical channels
2. Downlink
 The DL-SCH is mapped to the physical downlink shared channel (PDSCH).
 The BCH is mapped to the physical broadcast channel (PBCH).
 The PCH is mapped to the PDSCH.
Figure 3-2 shows the mapping between downlink transport channels and downlink physical
channels:
Figure 3-2 Mapping between downlink transport channels and downlink physical channels
Benefits
3.3.3 Physical Channel Management

Description
The physical layer hosts functions such as coding, physical-layer hybrid automatic repeat
request (HARQ) processing, modulation, multi-antenna processing, and mapping from signals
to appropriate physical time-frequency resources. Based on mapping, a higher-layer transport
channel can provide services to one or more physical channels at the physical layer.
Each physical channel corresponds to a set of resource elements carrying the information
from higher layers.

Downlink physical channels include:

 PBCH
 Physical downlink control channel (PDCCH)
 PDSCH
Uplink physical channels include:
 Physical uplink control channel (PUCCH)
 PUSCH
 PRACH
Benefits
3.3.4 Basic Performance of Uplink Control Channels

Description
Uplink control channel transmission involves the following events:
 Uplink data arrival, during which resource requests must be initiated
 Scheduling feedback on downlink service transmission
 CSI-RS scheduling triggered by services
The PUCCH carries UE information, such as PDSCH ACK/NACK, CSI measurement
information, and scheduling requests (SRs). The gNodeB can only perform procedures such
as PDSCH retransmission processing, CQI adjustment, and PMI weighting once the
information is received.
Differing in their resources, there are two types of PUCCH: short PUCCH and long PUCCH.
PUCCH Format Number of UCI Number of Description

Bits Symbols
Short Format 0 ≤2 1 to 2 SR
PUCCH HARQ-ACK having 2 or
fewer bits
SR+HARQ-ACK
Format 2 >2 1 to 2 HARQ-ACK having
more than two bits
CSI
HARQ-ACK+CSI+/SR
HARQ-ACK+SR
CSI+SR
Long Format 1 ≤2 4 to 14 SR
PUCCH HARQ-ACK having 2 or
fewer bits
SR+HARQ-ACK

Format 3 >2 4 to 14 HARQ-ACK having

more than two bits
CSI
HARQ-ACK+CSI+/SR
HARQ-ACK+SR
CSI+SR
The PUCCH scheduler ensures availability of dedicated semi-persistent PUCCH resources

when a UE initiates activities such as PDSCH scheduling and CSI-RS measurements, or
applies for uplink resources, and dynamically allocates PUCCH resources.
For PUCCH resource allocation, when a UE accesses the network:
 The PUCCH parameters of the UE are configured through RRC signaling. Example
parameters include the format, resource position, and DMRS density. These parameters
are required for CSI-RS scheduling, measurements, and feedback.
 If no semi-persistent dedicated PUCCH resource position is configured for the UE, the
PUCCH scheduler allocates HARQ feedback resources or CSI resources.
Benefits
This feature provides the basis for UEs to access an NR system and transmit data. Uplink
control channel transmission is a basic 5G function. Over the uplink control channel, UEs
transmit HARQ feedback, SRs, and CSI.
3.3.5 Basic Performance of Downlink Control Channels

Description
The PDCCH transmits the following three types of downlink control information (DCI):
 Downlink grant: includes the PDSCH resource indication, modulation and coding
scheme (MCS), HARQ information, and PUCCH power control commands.
 Uplink grant: includes the PUSCH resource indication, MCS, HARQ information, and
PUSCH power control commands.
 Power control command: a group of PUSCH power control commands for a UE, which
supplement PUSCH power control commands in uplink grants.
The gNodeB allocates a PDCCH according to the following conditions:
 When allocating PUSCH resources to a UE, the gNodeB allocates PDCCH resources to
the UE.
 When allocating PDSCH resources to a UE, the gNodeB allocates PDCCH resources to
the UE.
 When sending power control commands to a group of UEs, the gNodeB allocates
PDCCH resources to these UEs.
 When scheduling broadcast and multi-cast messages such as RMSI and paging messages,
the gNodeB allocates PDCCH resources.

Benefits
This feature provides the basis for UEs to access an NR system and transmit data. Downlink
control channel transmission is a basic 5G function. Through a downlink control channel
transmission process, UEs obtain broadcast message resources, PDSCH resources, PUSCH
resources, and power adjustment information.
3.3.6 Uplink Timing Basic Performance

Description
Uplink timing is a basic 5G function. Continuous uplink timing adjustments maintain uplink
synchronization for UEs by guaranteeing the time of uplink data from different UEs (data
reaches the gNodeB within an acceptable range), ensuring uplink data demodulation
performance.
Uplink timing includes initial uplink timing adjustment during random access and uplink
timing adjustment after random access succeeds.
 Initial uplink timing adjustment during random access: The gNodeB measures the uplink
timing value of the UE based on the PRACH signal, and sends the measurement result to
the UE.
 Uplink timing adjustment after successful random access: The gNodeB measures the
uplink timing value of the UE based on the SRS and DMRS, and sends the measurement
result to the UE.
Benefits
This feature provides the basis for UEs to maintain uplink synchronization.
3.3.7 SRS Basic Performance

Description
Sounding reference signal (SRS) is fundamental for 5G. SRS measurements enable channel
detection, which provides input for functions such as frequency selectivity, uplink timing,
downlink beamforming, uplink beam selection, rank adaptation, MCS selection, and uplink
power control, ensuring optimal transmission parameter selection in the uplink and downlink.
SRS basic performance includes SRS measurements, SRS beam scanning, SRS resource
allocation, and SRS scheduling.
 SRS measurement: interference noise measurements, post-equalization SINR
measurements, pre-equalization SINR measurements, channel response measurements,
timing advance (TA) measurements, and RI/PMI/CSI (3I) measurements
− SRS noise measurements are used for pre-equalization SINR calculation of the SRS
and SRS TA calculation in the serving cell.
− Post-equalization SINR measurements are mainly used for uplink scheduling
algorithms. In the serving cell, post-equalization SINR measurements include the
combined SINR measurements on the RB (used for the full-band SINR and
subband SINR calculation) and combined SINR measurements on the SRS
bandwidth (uplink AMC and uplink MIMO mode switching).

− Channel response measurements apply to uplink scheduling algorithms and virtual

MIMO pairing (for the orthogonality of UEs during the pairing and the SINR
calculation after the pairing).
− Pre-equalization SINR measurements of the SRS are used for SRS channel
estimation in the serving cell.
− TA measurements are used to maintain uplink time synchronization.
− 3I measurements are used for uplink and downlink scheduling.
 SRS beam scanning: Through SRS measurements in different beams, the scanning aims
to select the optimal receive beam for uplink data and control channels.
 SRS resource allocation: The gNodeB allocates periodic SRS resources and aperiodic
SRS resources to UEs in a cell.
− User-specific periodic SRS resources include user-specific SRS periods,
user-specific SRS bandwidths, SRS ports, and other resources.
− User-specific aperiodic SRS resources include user-specific SRS bandwidths, SRS
ports, and other resources.
 SRS scheduling: The gNodeB schedules aperiodic SRSs for UEs in a cell.
− SRS scheduling is triggered by events, such as uplink and downlink data
transmission requests and TA measurement requirements
− During scheduling, the scheduled user and scheduling resources are selected
according to the user priority and available resources.
Benefits
SRS enables the gNodeB to obtain channel information. Based on channel information,
functions such as frequency selection, beamforming, handovers between cells, and uplink
beam selection can be implemented to ensure optimal system performance.
3.3.8 Random Access

Description
Random access is a basic 5G function. Random access enables a UE to maintain uplink
synchronization and request for a connection setup with a gNodeB. It applies for the
following five events:
 Initial access from RRC_IDLE
 RRC connection reestablishment
 Handover
 Downlink data arrival
 Uplink data arrival
Random access enables a UE to maintain uplink synchronization and request for a connection
setup with a gNodeB.
Random access can be either contention-based (applicable to all preceding events) or
non-contention-based (only applicable to handovers and downlink data arrival). Transmission
is only allowed in uplink and downlink after random access succeeds.
There are four steps for contention-based random access:

1. The UE randomly selects the Random Access Preamble and transmits it through the
available PRACH. The available PRACH is set based on the PRACH configuration of
the cell.
2. The gNodeB transmits a Random Access Response after receiving the Random Access
Preamble.
3. After receiving the Random Access Response, the UE performs the first scheduled
uplink transmission over the UL-SCH.
4. The gNodeB sends the Contention Resolution message over the DL-SCH based on the
first scheduled uplink transmission and checks whether the UE has successfully accessed
the network.
There are three steps for non-contention-based random access:
 The gNodeB allocates the Random Access Preamble and PRACH resources to the UE
through dedicated signaling messages to request the UE to initiate random access.
 The UE transmits the Random Access Preamble over the allocated PRACH.
 The gNodeB transmits a Random Access Response after receiving the Random Access
Preamble. The UE successfully accesses the network when it receives the Random
Access Response.
In addition, the Huawei gNodeB supports random access preamble formats 0 and C2.
Benefits
This feature provides the basis for UEs to access an NR system.
3.4 FBFD-010010 Power Control

Availability
Summary
This feature provides the following functions:
 Physical random access channel (PRACH) power control
 Physical uplink shared channel (PUSCH) power control
 Physical uplink control channel (PUCCH) power control
 Sounding reference signal (SRS) power control
 Physical broadcast channel (PBCH) power control
 Synchronization signal (SS) power control
 Physical downlink control channel (PDCCH) power control
 Tracking reference signal (TRS) power control
 Physical downlink shared channel (PDSCH) power control
In NR, uplink power control enables gNodeBs to control the uplink transmit power of UEs in
a way that can reduce the UE power consumption with uplink service quality guaranteed and
improved. Uplink power control is applicable to the PRACH, PUSCH, PUCCH, and SRS.
Downlink power control enables gNodeBs to control the downlink transmit power of each

physical channel in a way that can reduce the gNodeB power consumption with downlink
service quality guaranteed and improved. Downlink power control is applicable to the PBCH,
SS, PDCCH, TRS, and PDSCH.
Benefits
This feature is one of the most important basic features of the NR system and is used to
guarantee and improve UE service experience.
Enhancement
None
Dependency
 Hardware
Downlink power control requires the following RF modules: NR TDD-capable pRRUs,
NR TDD-capable massive MIMO AAUs, and NR FDD-capable RRUs. It has no special
requirements for base station models, baseband processing units, and main control
boards.
Uplink power control has no special requirements for base station models, baseband
processing units, main control boards, and RF modules.
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.4.1 PRACH Power Control

Description
The PRACH is used for random access and uses open-loop power control.
This function enables the gNodeB and UEs to perform the following operations:
 It enables the gNodeB to deliver power control parameters, such as the expected initial
receive power and power ramping step, through broadcast messages.
 It enables UEs to calculate the transmit power for the initial random access preamble
based on the estimated downlink path loss and the power control parameters obtained by
monitoring the broadcast channel. If a random access attempt fails (for example, no
random access preamble response from a gNodeB is received), the UE will increase the
transmit power by a specified power ramping step and resend the preamble.
Benefits
PRACH power control can provide the following benefits:

 Ensuring that the preamble sent by the UE can be detected by the gNodeB
 Reducing UE power consumption
3.4.2 PUSCH Power Control

Description
The PUSCH is used to transmit uplink data and signaling messages and uses close-loop power
control.
The gNodeB dynamically adjusts the PUSCH transmit power based on the radio environment
of the UE.
When a UE initially accesses or is handed over to a cell, it calculates the initial transmit
power based on the parameters delivered by the gNodeB. During service provisioning, the
gNodeB uses closed-loop power control to adaptively adjust the PUSCH transmit power
based on the estimated transmit power spectral density (PSD) of the UE, the receive power
per RB, and channel quality to adapt to changes in the PUSCH channel environment and
service load.
Benefits
Through precise control of the UE transmit power on the gNodeB side, PUSCH power control
can provide the following benefits:
 Reducing the interference between neighboring cells and increasing the uplink
throughput of NG-RAN
 Ensuring the service quality, for example, meeting the requirements on block error rate
(BLER)
3.4.3 PUCCH Power Control

Description
The PUCCH is used to transmit the uplink control information (UCI) and uses close-loop
power control.
The gNodeB dynamically adjusts the PUCCH transmit power based on the radio environment
of the UE. PUCCH closed-loop power control includes inner-loop and outer-loop power
control. Inner-loop power control enables the gNodeB to periodically adjust the PUCCH
transmit power based on the difference between the measured signal to interference plus noise
ratio (SINR) and the target SINR on the PUCCH to adapt to changes in the PUCCH channel
environment. Outer-loop power control enables the gNodeB to dynamically adjust the target
SINR based on the bit error rate (BER) and BLER on the PUCCH.
Benefits
Through precise control of the UE transmit power on the gNodeB side, PUCCH power
control can provide the following benefits:
 Ensuring the UCI feedback performance, that is, meeting the requirements on BER

3.4.4 SRS Power Control

Description
The SRS is used to detect uplink channel quality and uses close-loop power control.
SRS power control uses parameter settings and TPC for PUSCH power control. The SRS
transmit power is determined based on the transmission bandwidth and PUSCH power control
parameters.
Benefits
SRS power control can provide the following benefits:
 Ensuring that the received signal quality of SRS meets the detection requirements
3.4.5 PBCH Power Control

Description
PBCH power control ensures the cell coverage performance of the PBCH. Because the PBCH
carries cell-level signals, dynamic power control cannot be performed.
Benefits
PBCH power control can provide the following benefits:
 Ensuring that the PBCH data sent by the gNodeB can be correctly demodulated by all
UEs in the cell
 Reducing gNodeB power consumption
3.4.6 SS Power Control

Description
SS power control ensures the cell coverage performance of the SS. Since the SS is
cell-specific, dynamic power control cannot be performed.
Benefits
SS power control can provide the following benefits:
 Ensuring that the SS sent by the gNodeB can be correctly demodulated by all UEs in the
cell

3.4.7 PDCCH Power Control

Description
When the total symbol power is fixed, PDCCH power control increases the PDCCH transmit
power for cell edge UEs, improving the coverage performance of the control channel for the
cell.
Benefits
PDCCH power control can improve the downlink control channel coverage.
3.4.8 TRS Power Control

Description
TRS power control ensures the cell coverage performance of the TRS. Since the TRS is
cell-specific, dynamic power control cannot be performed.
Benefits
TRS power control can provide the following benefits:
 Ensuring that the TRS sent by the gNodeB can be correctly demodulated by all UEs in
the cell
3.4.9 PDSCH Power Control

Description
PDSCH power control allows the gNodeB to adjust the PDSCH power based on the channel
quality and cell resource usage, ensuring the PDSCH capacity and coverage performance.
Benefits
PDSCH power control can provide the following benefits:
 Ensuring the service quality, for example, meeting the requirements on BLER
 Increasing user throughput
3.5 FBFD-010011 Scheduling

Availability

Summary
This feature uses the proportional fair (PF) scheduling algorithm to allocate resources to UEs
in each TTI. It also supports uplink frequency selective scheduling, joint optimization of
uplink multi-CC power control scheduling, and enhanced HARQ adaptive retransmission for
eMBB services.
Benefits
The scheduling algorithm helps achieve a trade-off between system capacity and user
experience.
Enhancement
5G RAN2.0 introduces TDD non-massive MIMO uplink discontinuous frequency selective
scheduling, CBG-based HARQ feedback and retransmission, and enhanced adaptive
retransmission.
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.5.1 Uplink Non-Consecutive Scheduling

Description
Based on uplink CP-OFDM waveforms, this function allocates multiple segments of
non-consecutive uplink resource blocks (RBs) to UEs, with frequency selective scheduling
enabled for each segment.
The non-consecutive resource allocation is achieved by selecting the resource block groups
(RBGs) for UEs with CP-OFDM waveforms and combining the single-UE resource allocation
and pairing processes.
Benefits
In addition to delivering uplink frequency selection gains, this function maximizes uplink RB
utilization, increases uplink throughput, and provides better user experience.

3.5.2 Enhanced Adaptive Retransmission

Description
Downlink adaptive retransmission can deliver combination gains. Therefore, in a common
downlink scenario, by accurately estimating an MCS required for retransmission and then
reducing the number of RBs required for retransmission, resources can be saved for new
transmission of other UEs. In this way, spectral efficiency can be improved in addition to
combination gains.
Based on the measurement feedback, the gNodeB estimates the demodulation capability
difference between the initial transmission and retransmission of a UE and accurately adjusts
the RB resources required at the retransmission time. The saved resources are allocated to
other UEs for new transmission.
Benefits
This feature saves resources required for retransmission and improves spectral efficiency.
3.6 FBFD-010013 Radio Interface Ciphering

Availability
Summary
This feature involves the AES, SNOW 3G, and ZUC ciphering algorithms, which are used to
cipher signaling and service data transmitted between UEs and base stations.
Benefits
Ciphering algorithms protect signaling and service data against unauthorized interception and
tampering.
Description
The base station provides ciphering protection for RRC signaling messages and user-plane
messages at the PDCP layer.
In a non-standalone (NSA) scenario, after receiving the UE security context from the master
base station, the gNodeB selects a ciphering algorithm based on the algorithm priority
configuration on the gNodeB and calculates the cipher key.
In a standalone (SA) scenario, the gNodeB selects a ciphering algorithm during an AS
security mode command (SMC) procedure. The cipher key for RRC signaling is derived and
RRC signaling ciphering is activated during the AS SMC procedure. User-plane ciphering
activation is determined by the security policy delivered by the core network. The user-plane
cipher key is derived during the user-plane bearer setup procedure.
The ciphering algorithm changes only when the UE is handed over between cells. It is
renegotiated based on the gNodeB ciphering algorithm priority and the UE capability. Cipher

keys can be changed during handovers, RRC connection resume, or RRC connection
reestablishments. Intra-cell handovers can also change cipher keys of the UEs in
RRC_CONNECTED mode.
Enhancement
None
Dependency
 Hardware
None
 UE
UEs support 5G radio interface ciphering algorithms.
 Core network
None
 Other NEs
None
 Other features
None
3.7 FBFD-010014 Mobility Management

Availability
Summary
This feature provides the following functions:
1. Basic functions for mobility management
2. Intra-NR coverage-based intra-frequency handover
3. Intra-NR coverage-based inter-frequency handover
4. Intra-NR frequency-priority-based inter-frequency handover
5. Multi-band compatibility
Benefits
This feature helps ensure continuous wireless network coverage to enable consistent service
experience on UEs.
Enhancement
 5G RAN2.1
Intra-frequency handover is supported in Standalone (SA) networking.
 5G RAN3.0

Coverage-based inter-frequency handover and frequency-priority-based inter-frequency

handover are supported in SA networking.
 5G RAN3.1
Multi-band compatibility is supported in SA and NSA networking.
Dependency
 Hardware
None
 UE
The EN-DC mobility requires UEs to support LTE and NR DC.
 Core network
None
 Other NEs
None
 Other features
None
3.7.1 Basic Functions for Mobility Management

Description
Introduced in 5G RAN1.0, this function provides mobility management for changing a
primary secondary cell (PSCell) under a secondary gNB (SgNB) for UEs in connected mode
in an NR cell on an EN-DC network.
By scenario, the modifications are classified into two procedures:
1. SgNB Modification procedure
A PSCell of an SgNB is changed, and another cell under the same SgNB becomes a
PSCell.
2. SCG Change procedure
A PSCell under a SgNB is changed, and a cell under other gNodeBs becomes a PSCell.
Benefits
Mobility requirements are fulfilled for UEs supporting EN-DC in an NR cell.
3.7.2 Intra-NR Coverage-based Intra-Frequency Handover

Description
A coverage-based intra-frequency handover is triggered when a UE receives signals of a
better quality from intra-frequency neighboring cells than from the serving cell. The
frequency is the same for the target neighboring cell and the serving cell. A coverage-based
intra-frequency handover includes three phases: measurement, handover decision, and
handover execution.
1. Measurement

The gNodeB delivers measurement configurations through an RRC Reconfiguration message.

Measurement configurations include target frequencies, measurement quantity,
handover-triggering event parameters, and measurement result reporting parameters. The UE
makes handover event decisions and triggers measurement reporting based on measurement
configurations.
2. Handover decision
The gNodeB determines whether to initiate handover preparation based on the measurement
reports.
3. Handover execution
Based on handover preparation results, the gNodeB sends a handover command to the UE
through an RRC Reconfiguration message. Then, the UE performs handover.
Intra-frequency handovers support three handover procedures:
Intra-gNodeB handover: The source cell and target cell of a handover belong to the same
gNodeB.
Inter-gNodeB Xn-based handover: The source cell and target cell of a handover belong to
different gNodeBs that exchange information through the Xn interface.
Inter-gNodeB Ng-based handover: The source cell and target cell of a handover belong to
different gNodeBs that exchange information through the Ng interface, but not through the
Xn interface.
Benefits
Coverage continuity is ensured for UEs moving among intra-frequency cells to reduce the
service drop rate and improve user experience.
3.7.3 Intra-NR Coverage-based Inter-Frequency Handover

Description
Inter-frequency handover ensures RRC_CONNECTED UEs to receive continuous services
when moving across different cells operating at different frequencies. An inter-frequency
handover includes four phases: handover function start decision, measurement configuration
delivery, handover decision, and handover execution.
1. Handover Function Start Decision
Inter-frequency measurements are triggered by event A2 and stopped by event A1. When
the gNodeB receives an event A2 report for coverage-based inter-frequency
measurements, the inter-frequency handover function is started.
2. Measurement configuration delivery
In inter-frequency measurements, the gNodeB sends the event A5 measurement
configurations to the UE through an RRC Reconfiguration message. When the RSRP
meets the criteria set in the measurement configurations, the UE sends measurement
reports to the gNodeB. Upon receiving a measurement report from the UE, the gNodeB
makes a handover decision.
3. Handover decision
The gNodeB determines whether to initiate handover preparation based on the
measurement reports.

4. Handover execution
Based on handover preparation results, the gNodeB sends a handover command to the
UE through an RRC Reconfiguration message. Then, the UE performs handover.
Inter-frequency handover applies to the following scenarios:
 Intra-gNodeB handover: The source cell and target cell of a handover belong to the same
gNodeB.
 Inter-gNodeB Xn-based handover: The source cell and target cell of a handover belong
to different gNodeBs that exchange information through the Xn interface.
 Inter-gNodeB NG-based handover: The source cell and target cell of a handover belong
to different gNodeBs that exchange information through the NG interface, but not
through the Xn interface.
Benefits
In multi-frequency networking, coverage continuity is ensured for UEs moving among
inter-frequency cells to reduce the service drop rate and improve user experience.
3.7.4 Intra-NR Frequency-Priority-based Inter-Frequency

Handover
Description
In multi-frequency co-coverage networking, operators can set a frequency priority for each
frequency. When the frequency-priority-based inter-frequency handover algorithm is enabled,
event A1 is used to trigger inter-frequency measurement for event A4. When the
inter-frequency RSRP meets the criteria set in the measurement configurations, the UE sends
measurement reports to the gNodeB. Upon receiving a measurement report from the UE, the
gNodeB selects a cell with a higher frequency priority for handover decision.
Benefits
This function provides a means to transfer UEs and allows for flexible networking to help
operators implement service steering.
3.7.5 Multi-Band Compatibility

Description
Information about the frequency bands supported by an NR cell is sent to UEs through SIB
broadcast, and each cell can work in multiple frequency bands. After a UE receives the
frequency band information indicated in the SIB broadcast, the UE selects a frequency band
matching its own band capability for access. The Multi-Band Compatibility function extends
the SIB messages as follows:
 SIB1: contains the multi-band indicator of the serving cell.
 SIB4: contains the multi-band indicators of inter-frequency neighboring cells.
An NR cell and its neighboring NR cells can both work in multiple frequency bands and the
preceding types of SIBs are sent to UEs.

If a UE supports any of the frequency bands in which a cell works, the UE can access the cell.
This allows more UEs to access the network.
If a UE supports any of the frequency bands configured for a neighboring cell, the UE can be
handed over to this cell. More candidate cells are therefore available for a UE handover.
Benefits
 This function allows UEs supporting different frequency bands to access the network,
increasing the number of UEs served by an operator and making full use of spectrum
resources. For example, if a cell is configured with both frequency bands n77 and n78,
UEs supporting either n77 or n78 can access the cell.
 UEs can access and roam to more networks operating in different frequency bands,
easing the UE management and operation.
3.8 FBFD-010015 Basic Beam Management

Availability
Summary
The Beam Management feature enables broadcast channels to use narrow beams. Through
beam scanning, the best beam can be found for synchronization and system information
demodulation. This improves the cell coverage.
The Beam Management feature enables control channels to use narrow beams. The gNodeB
tracks and maintains the best beams of UEs to effectively extend the coverage area of the
control channels.
Benefits
This feature extends the coverage area of broadcast channels and control channels.
This feature applies to different networking scenarios. It improves coverage and reduces
interference.
Description
Broadcast Channel Beam Management
Broadcast channels use SS/PBCH blocks (SSBs) for beam sweeping. Each SSB sends one
beam. According to 3GPP specifications, the C-band provides a maximum of eight SSBs.
Multiple beams serve an entire cell in polling mode. The polling of narrow beams provides
better coverage than LTE wide beams. It is because the beam is narrower when the transmit
power of each narrow beam is the same as that of the LTE wide beam.

Figure 3-3 NR broadcast beam scanning
In the default coverage scenario of a C-band 32T or 64T AAU cell, the horizontal 3 dB
beamwidth is 105°, and the vertical 3 dB beamwidth is 6°.
In the default coverage of a 8T or lower RRU, the horizontal and vertical beamwidths are
subject to external antennas.
Control Channel Beam Management
The UE sends SRS signals, and the gNodeB maintains the optimal SRS measurement beam
set and then configures it as the transmit or receive beams of the control channels.
TRS uses wide beams to cover the entire cell.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.9 FBFD-020101 Reliability

Availability
This feature is available as of 5G RAN2.0. Cell outage detection and recovery in SA
networking, cold backup of main control boards, and inter-board baseband resource
redundancy functions are introduced in 5G RAN2.1. Cell outage detection based on the cell
sleeping state is introduced in 5G RAN3.0.

Summary
This feature includes flow control, base station always online, cell outage detection, cold
backup of main control boards, and inter-board baseband resource redundancy.
Benefits
This feature ensures the reliability of base stations, cuts down the impact scope and duration
of faults, and lowers the number of accidents during network operation. The feature also helps
to reduce the demand for onsite maintenance and improves O&M efficiency, enhancing
operators' brand image.
Enhancement
 5G RAN2.1
Cell outage detection and recovery in SA networking and flow control in SA networking are
enhanced.
Cold backup of main control boards and inter-board baseband resource redundancy are
introduced.
 5G RAN3.0
Cell outage detection based on the cell sleeping state is introduced.
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
3.9.1 Flow Control

Description
With flow control, a device controls input and output flows to prevent the device from being
overloaded and maintain device stability. Flow control is performed on signaling, service, and
operation and maintenance (O&M) data. Flow control is achieved by the following two
methods:
 Input flows are restricted to prevent the device from being overloaded and ensure the
processing capability of the device when its service traffic dramatically increases.
 Output flows are restricted to prevent the peer device from being overloaded.

Flow control is performed on control-plane and user-plane data flows within a gNodeB or
between a gNodeB and an external NE.
Flow control methods are as follows:
 Restricting output flows of the gNodeB or reducing the data flows received from the peer
NE through backpressure
 Reducing gNodeB's output data rate or decreasing the output data rate of the peer NE
through backpressure
 Identifying service priorities and controlling access of low-priority data flows
Benefits
When heavy traffic exists on the device, flow control can reduce the device reset risk and
improve device reliability. Flow control also prevents the deterioration of the access success
rate and handover success rate to ensure user experience.
3.9.2 Cell Outage Detection

Description
Cell outage refers to scenarios where a UE cannot access cell services or where there is
significant key performance indicator (KPI) deterioration due to faults or alarms. Cell outage
significantly affects network performance and user experience, especially on single-frequency
and single-RAT networks.
Cell outage detection enables Huawei base stations automatically detect cell outages,
shortening the cell outage duration. Cell outage detection is used throughout the network
lifecycle.
Cell outage may be caused by:
 Software or hardware faults detected by the gNodeB
Such faults include faults in an RRU, baseband processing unit (BBP), common public
radio interface (CPRI) port, feeder, power supply system, and transport link (such as an
S1 link).
 Unknown software and hardware faults
Such faults refer to software or hardware faults that cannot be detected by a gNodeB and
do not trigger any alarms, such as faults on common or physical channels.
A gNodeB detects cell outage based on:
 Alarms: The gNodeB checks software and hardware and determines cell outage upon
detecting cell unavailability alarms.
 Abnormal preset KPIs: The gNodeB determines cell outage based on KPIs including the
RRC setup success rate, bearer setup success rate, and abnormal service drop rate.
 Cell sleeping state: The gNodeB checks for a sleeping cell based on the number of RRC
connection setup requests and the maximum number of UEs in RRC_CONNECTED
state in a cell.

Benefits
The cell outage detection feature enables gNodeBs to quickly detect cell outage, shorten the
cell outage duration, reduce the impact on user experience, and help to improve operators'
brand image.
3.9.3 Base Station Always Online

Description
The remote operation and maintenance channel (abbreviated as OM channel) of a base station
refers to the channel through which an eGBTS/NodeB/eNodeB/gNodeB communicates with
the MAE or a GBTS communicates with a BSC to exchange base station management and
O&M information.
If an OM channel is interrupted, measures are taken to recover the OM channel. These
recovery measures include the following:
 Automatic version rollback
 Automatic configuration data rollback
 Transmission link fault rectification
 Automatic OM channel establishment
 Automatic recovery of OM channel running data
Automatic version rollback: After an upgrade of base station software, the software version is
automatically rolled back to the source version, when rollback conditions are met, to recover
the OM channel.
Automatic configuration data rollback: Users enable this function before modifying the data
related to the OM channel. If the OM channel continuously disconnects after the modification
when the timer specifying the rollback time expires, the base station automatically resets and
rolls the configuration data back to the data before modification to recover the OM channel.
Transmission link fault rectification: The base station is automatically reset to recover the
faulty OM channel when both the OM channel and services are continuously interrupted.
Automatic OM channel establishment: After this function is enabled, the base station obtains
the OM channel information through the DHCP Detect process to recover the OM channel
when automatic OM channel establishment conditions are met.
Automatic recovery of OM channel running data: The OM channel running data collected
while the OM channel works properly is used to restore the OM channel.
Benefits
The base station OM channel self-recovery function eliminates the need of onsite handling in
the case of an OM channel interruption, and therefore shortens the interruption time and saves
costs.
3.9.4 Cold Backup of Main Control Boards

Description
If a base station is configured with only one main control board, the failure of the board will
cause long-time service outage of the base station. To support cold backup of main control

boards, two main control boards working in active/standby mode are required. When a fault is
detected on the active main control board, the active and standby boards switch roles.
Services can be automatically recovered after the services carried on the originally active
board are interrupted. This improves base station reliability. This feature requires that the two
main control boards are of the same type.
Cold backup of main control board involves active/standby competition, data backup, and
active/standby switchover.
Benefits
When the active main control board becomes faulty, the standby main control board becomes
active and continues to provide services, reducing service interruption duration and increasing
customer satisfaction.
3.9.5 Inter-Board Baseband Resource Redundancy

Description
If a baseband processing unit (BBP) becomes faulty, the cells served by this failed BBP will
be affected. With this feature, a base station can be configured with multiple BBPs to enable
inter-board redundancy. When one BBP becomes faulty, the cells served by the faulty BBP
can be reestablished on another operational BBP with available resources. This improves base
station reliability.
Benefits
When one BBP becomes faulty, the cells served by the faulty BBP can be reestablished on
another operational BBP with available resources. This improves base station reliability.
3.10 FBFD-020102 Radio QoS Management

Availability
This feature is available as of 5G RAN2.0 and is introduced to standalone (SA) architecture as
of 5G RAN2.1.
Summary
Quality of service (QoS) management ensures service quality by coordinating among all
network nodes involved, from service initiation to service response.
Radio QoS management consists of two phases: QoS management phase during service
initiation and QoS control phase after service initiation.
QoS management during service initiation includes the binding of services with appropriate
radio bearers, admission control, and preemption.
QoS control after service initiation includes differentiated scheduling of bearers, congestion
control, and flow control.

Benefits
Radio QoS management binds users to appropriate radio bearers, ensuring QoS for services of
different levels and enabling more users to have access to limited spectrum resources. In
addition, radio QoS management provides services that match user requirements and ensures
differentiation and fairness among multiple users.
Description
The current version supports radio QoS management in non-standalone (NSA) architecture
and SA architecture.
 When a UE initiates a service setup request, the gNodeB binds the service to a proper
bearer based on the QoS attributes, such as QoS class identifier (QCI) and 5G QoS
indicator (5QI) characteristics. In addition, an operator can adjust Packet Data
Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control
(MAC) parameters for each bearer as required.
 After the bearer is established, differentiated scheduling is provided based on the settings
of each bearer's parameters, channel quality, and history rate to satisfy the QCI and 5QI
characteristics of each bearer in table 6.1.7-A "Standardized QCI characteristics" for
NSA in 3GPP TS 23.203 and in table 5.7.4-1 "Standardized 5QI to QoS characteristics
mapping" for SA in 3GPP TS 23.501.
Non-guaranteed bit rate (GBR) services support the limitation on aggregate maximum
bit rates (AMBR) for UEs and minimum rate guarantee.
Enhancement
The capability of the 5G RAN2.1 is enhanced to support the SA architecture.
Dependency
 Hardware
None
 UE
None
 Core network
Evolved packet core (EPC) in NSA architecture and 5G Core Network (5GC) in SA
architecture
 Other NEs
None
 Other features
None
3.11 FBFD-021102 Integrity Protection

Availability

The PDCP Counter Check feature is introduced as of 5G RAN3.0.
Summary
This feature covers the AES, SNOW 3G, and ZUC integrity protection algorithms. These
algorithms protect the integrity of signaling and user-plane data between UEs and base
stations to prevent data from being tampered with during transmission.
Benefits
This feature protects signaling and user-plane data from being tampered with.
Description
Base stations offer integrity protection for RRC signaling messages and user-plane messages
at the PDCP layer. The sender calculates a message authentication code MAC-I based on an
RRC message or user-plane message by using an integrity protection algorithm, and then
sends the code to the receiver together with the message. The receiver calculates a code based
on the received RRC message or user-plane message by using the same integrity protection
algorithm and compares it against the MAC-I of the message from the sender. If the two codes
are different, the message has been tampered with.
In an SA scenario, the gNodeB selects an integrity protection algorithm during an AS SMC
procedure. The cipher key for RRC signaling integrity protection is derived and integrity
protection is activated during the AS SMC procedure. User-plane integrity protection
activation is determined by the security policy delivered by the core network. The user-plane
cipher key is derived during the user-plane bearer setup procedure.
In an NSA scenario, the gNodeB is connected to the EPC. Integrity protection is not involved
on the user plane and is supported on the control plane between the UE and the gNodeB.
Enhancement
PDCP Counter Check: If integrity protection is not enabled for user-plane messages, operators
can enable the PDCP Counter Check feature, which is used to check the consistency of the
PDCP counter values for user-plane data bearers between the UE and gNodeB.
Dependency
 Hardware
None
 UE
UEs support 5G air interface integrity protection.
UEs support PDCP Counter Check.
 Core network
None
 Other NEs
None
 Other features
None

3.12 FBFD-021103 DRX

Availability
Summary
This feature supports discontinuous reception (DRX), differentiated UE DRX parameter
settings, and ANR measurement.
Benefits
Compared with continuous reception, DRX has the following benefits:
 Reduces power consumption and prolongs the standby time of UEs. A UE does not need
to continuously monitor the physical downlink control channel (PDCCH). Therefore, the
UE can turn off its receiver.
 Allows the UE to perform ANR measurement during the sleep time in DRX.
Description
When DRX is used, the UE does not continuously monitor the PDCCH. A DRX cycle
consists of active time and sleep time, corresponding to the active state and sleep state,
respectively. In active time, the UE turns on its receiver, monitors the PDCCH, and receives
downlink data and signaling. In sleep time, the UE neither monitors the PDCCH nor receives
downlink data and signaling, and it can turn off its receiver, reducing power consumption. In
non-DRX mode, the UE always turns on its receiver and stays in the active state.
Enhancement
None
Dependency
 Hardware
mmWave is not supported.
 UE
UEs need to support DRX.
 Core network
None
 Other NEs
None
 Other features
None

3.13 FBFD-021104 SA Option 2 Architecture

Availability
Summary
SA is short for standalone and indicates standalone networking. The SA Option 2 architecture
is an end-to-end 5G network architecture, which adopts 5G standards through the whole
process covering the terminals, NR air interface, and core network. The purpose is to support
5G interfaces and provide 5G functions and services.
Benefits
SA Option 2 Architecture provides diversified services that cannot be carried by 4G networks.
The examples include large-bandwidth, low-latency, and high-reliability service applications,
network slicing services, as well as new business models such as mobile edge computing.
This feature can also provide scenario-based customized services to meet various service
requirements.
Description
The SA Option 2 Architecture includes the 5GC and NG-RAN. The 5GC mainly comprises
the access and mobility management function (AMF) and the user plane function (UPF), and
the NG-RAN comprises the gNodeBs. The following describes the interfaces between NEs:
 NG-C and NG-U: The gNodeB is connected to the AMF through the NG-C interface to
implement NG control plane functions. The gNodeB is connected to the UPF through the
NG-U interface to implement NG user plane functions.
 Xn-C and Xn-U: gNodeBs are connected through Xn-C and Xn-U interfaces to
implement Xn control plane and user plane functions, respectively.
 Uu: The gNodeB is connected to the UE through the Uu interface to implement NR air
interface functions.
The NG and Xn interfaces support self-configuration. They can automatically obtain the
transport and network layer addresses of the peer end, and allow automatic management
based on link status and peer status. They also support the following functions:

 NG interface: self-setup, self-update, and self-removal

 Xn interface: self-setup, self-update, and self-removal
Enhancement
 5G RAN3.0
The NG-flex is introduced to interconnect with the AMF pool, thereby ensuring the reliability
of E2E networking.
Dependency
 Hardware
 UE
5G terminals
 Core network
5GC
 Other NEs
None
 Other features
None
3.14 FBFD-031102 Inactive State

Availability
Summary
This feature supports mobility management for UEs in RRC_INACTIVE state in the SA
networking of an NR network. Mobility management in this state includes cell search, PLMN
selection, cell selection, cell reselection, RAN-based Notification Area (RNA) update, as well
as state transition with RRC_CONNECTED and with RRC_IDLE.

Benefits
UEs in RRC_INACTIVE state can maintain similar power consumption as in RRC_IDLE
mode while resuming data transmission within a short delay.
Description
In an NR network, a UE can be in RRC_IDLE, RRC_CONNECTED, or RRC_INACTIVE
state. The cell search, PLMN selection, cell selection, and cell reselection procedures in
RRC_INACTIVE state are the same as those in RRC_IDLE state. The RNA update and state
transition with RRC_CONNECTED and RRC INACTIVE states are new to
RRC_INACTIVE state.
 RNA update
The RNA update procedure applies to the following scenarios:
− A UE periodically sends RNA update information to the base station, so that the
base station determines whether the UE is disconnected from the network.
− After cell reselection, a UE notifies the base station through an RNA update
message if the UE finds that the RNA ID of the new cell is different from the latest
obtained RNA ID.
 RRC_CONNECTED to RRC_INACTIVE
If a UE does not send or receive data within the period specified by the inactivity timer,
the UE enters RRC_INACTIVE state.

 RRC_INACTIVE to RRC_CONNECTED
In case of RAN paging or uplink data transmission, the UE is restored from
RRC_INACTIVE to RRC_CONNECTED state.
 RRC_INACTIVE to RRC_IDLE
If no data is transmitted or received before the timer for transiting from
RRC_INACTIVE to RRC_IDLE state expires, the UE enters RRC_IDLE state.
Enhancement
None
Dependency
 Hardware
 UE
UEs must support the RRC_INACTIVE state.
 Core network
None
 Other NEs
None
 Other features
None

5G RAN3.1 Basic Feature Description 4 Transmission & Security
4 Transmission & Security
4.1 FBFD-010016 Transmission Networking

4.2 FBFD-010017 CPRI Compression
4.3 FBFD-010018 Basic QoS Management
4.4 FBFD-010019 VLAN Support (IEEE802.1p/q)
4.5 FBFD-010020 Synchronization
4.6 FBFD-010022 Active/Standby IP Routes
4.7 FBFD-010023 Security Mechanism
4.8 FBFD-010024 IP Performance Monitoring
4.9 FBFD-021101 IPv4/IPv6 Dual Stack
4.10 FBFD-010025 Basic O&M Package
4.11 FBFD-031003 PSU Shutdown
4.1 FBFD-010016 Transmission Networking

Availability
Summary
gNodeBs support multiple network topologies, including star, chain, tree.
Benefits
Multiple network topologies are supported.
Enhancement
None

Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
This feature supports IPv6.
4.1.1 Star Topology

Description
Figure 4-1 Star topology
gNodeBs support star topology and are connected to the core network through layer 2 or layer
3 data networks. A gNodeB uses S1 and Ng interfaces to connect to a core network.
A gNodeB uses an X2 interface to connect to an eNodeB for information exchange.
A gNodeB uses an Xn interface to connect to another gNodeB for information exchange.
Benefits
 Simplest topology
 Easy management and high reliability

4.1.2 Chain Topology

Description
gNodeBs support the chain topology. This topology applies to belt-shaped and sparsely
populated areas, such as highways and railways. In these areas, the chain topology requires
less transmission equipment. However, the chain topology reduces network reliability since
signals are propagated through multiple intermediate NEs.
Figure 4-2 shows the chain topology.
Figure 4-2 Chain topology
Benefits
The chain topology requires less transmission equipment and reduces the transmission line
lease cost and construction cost.
4.1.3 Tree Topology

Description
gNodeBs support the tree topology. In most scenarios, a microwave network uses the tree
topology. This topology applies to microwave transmission.
This topology requires fewer transmission links than the star topology. However, the tree
topology reduces network reliability since signals are propagated through multiple
intermediate transmission media. Faults on a gNodeB may affect its lower-level gNodeBs.
This topology applies to wide and sparsely populated areas. Capacity expansion for networks
using this topology may require network reconstruction.
Figure 4-3 shows the tree topology.

Figure 4-3 Tree topology
Benefits
The tree topology requires fewer transmission links than the star topology.
4.2 FBFD-010017 CPRI Compression

Availability
Summary
This feature reduces the common public radio interface (CPRI) bandwidth required in a single
cell.
Benefits
The benefits of CPRI compression are as follows:
 Reduces the number of optical modules and optical fibers.
 Reduces investment on gNodeB installation and reconstruction.
 Enables the same interface bandwidth to support more carriers.
Description
With CPRI Compression, the CPRI bandwidth required by each single cell is reduced.
Essentially, with the cell bandwidth and the antenna quantity unchanged, CPRI Compression
decreases the transmission bandwidth used by each optical module or the quantity of optical
modules and fiber optic cables. This reduces the investment on gNodeB installation and
construction.

The reduction in the CPRI bandwidth varies depending on the compression ratio of CPRI
Compression. Generally, in a 100 MHz 64T64R cell, 3.2:1 compression reduces the CPRI
bandwidth from 320 Gbit/s to 100 Gbit/s and therefore the number of 100 Gbit/s CPRI ports
from 4 to 1.
Enhancement
None
Dependency
 Hardware
Baseband processing boards and RF modules that support CPRI
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
4.3 FBFD-010018 Basic QoS Management

Availability
Summary
 Huawei gNodeBs support differentiated services (DiffServ) and provide quality of
service (QoS) guarantee by classifying and managing traffic flows.
 Differentiated transmission flow control ensures impartial UE access to a cell while
offering an extensive range of differentiated services. This is achieved using the
following functions:
− Queue scheduling, including priority queuing (PQ) and weighted round robin
(WRR)
− Back-pressure flow control
Benefits
 This feature provides a DiffServ QoS guarantee mechanism, which is a standard
mechanism within the industry.
 This feature enables differentiated transmission flow control to ensure impartial UE
access to a cell while offering an extensive range of differentiated services.
Description
 DiffServ

DiffServ is a QoS guarantee mechanism. It classifies traffic flows carrying IP packet

parameters into different classes and provides differentiated management on these traffic
classes. The IP packet parameters include DSCP and type of service (TOS).
The DiffServ mechanism involves three key concepts: classification, marking, and per-hop
behavior (PHB). Traffic classes with different PHBs are classified and marked.
PHB is defined as follows:
 Default PHB is typically applicable to best-effort traffic.
 Expedited forwarding (EF) PHB is dedicated to low-loss and low-latency traffic.
 Assured forwarding (AF) PHB is a behavior group.
 Class selector (CS) PHB maintains backward compatibility with the IP Precedence field.
5G traffic is classified based on the QoS class identifier (QCI) or 5G QoS indicator (5QI). The
mapping between QCIs/5QIs and DSCPs can be configured to mark traffic classes. DSCPs
are used to describe PHB priorities. Table 4-1 describes the mapping between QCIs and
DSCPs.
Table 4-1 Mapping between QCIs/5QIs and DSCPs
Traffic Class QCI/5QI Resource Type DSCP

User plane 1 Guaranteed bit rate (GBR) 46
2 34
3 34
4 34
5 Non-GBR 46
6 18
7 18
8 18
9 0
65 Guaranteed bit rate (GBR) 46
66 46
69 Non-GBR 46
70 18
Control plane Stream Control 48
Transmission
Protocol
(SCTP)
Operation and MML 46
maintenance (O&M)
File Transfer 18
Protocol (FTP)
IP clock 46

 Differentiated transmission flow control

This function ensures impartial UE access to a cell while offering an extensive range of
differentiated services. UEs with high priorities are preferentially served.
Implementation of this function requires queue scheduling and back-pressure flow control.
 Queue scheduling enables services to enter PQ queues and WRR queues based on
service priorities. Services in PQ queues have the highest scheduling priority. Services in
WRR queues are scheduled according to the weights that are calculated based on service
bandwidth. Each service has a weight and scheduling chance.
 Back-pressure flow control detects congestion overhead over the S1 or NG interface.
When congestion occurs, a message is first sent to the data source to indicate congestion,
and then some low-priority packets are discarded.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
4.4 FBFD-010019 VLAN Support (IEEE802.1p/q)

Availability
Summary
With this feature, the virtual local area network (VLAN) function differentiates traffic flows,
manages data priorities, and provides security scheduling at the MAC layer.
Benefits
 Traffic isolation at the MAC layer
 Priority management at the MAC layer
 Security assurance at the MAC layer

Description
The gNodeB supports the VLAN function in compliance with IEEE 802.1p/q. In this way,
traffic flows of different types are isolated at the MAC layer. For example, OM data and
traffic data are tagged with different VLANs. In addition, the data priority and security are
provided at the MAC layer.
VLAN tags are attached based on:
 Differentiated services code point (DSCP)
 Next-hop IP address
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
4.5 FBFD-010020 Synchronization

Availability
Summary
This feature allows synchronization with diversified clock sources, including the GPS,
BeiDou, 1PPS+TOD, BITS, and E1/T1.
Benefits
This feature supports the synchronization with diversified clock sources.
Enhancement
 5G RAN3.0
Added the clock out-of-synchronization detection function, which helps improve the
clock reliability.

 5G RAN3.1
Added synchronization with Galileo and network-wide synchronization deviation
detection.
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
None
 Other features
None
4.5.1 Clock Source Switching Manually or Automatically

Description
gNodeBs support synchronization with multiple clock sources. The clock source can be
conveniently and flexibly selected. Once a clock source fails, the clock in use can be manually
or automatically switched to another available one.
gNodeBs support the following clock sources:
 GPS clock
 IEEE1588 V2 clock synchronization
 Synchronous Ethernet
 IEEE 1588V2 and synchronous Ethernet combination
In addition to the previous clock sources, gNodeBs can work with the local oscillator.
Benefits
This feature enables manual or automatic switching between clock sources. If an error occurs
on the clock source in use, gNodeBs are not affected.
4.5.2 Synchronization with GPS

Description
gNodeBs can work with diversified clock sources to suit different clock topologies. The
Global Positioning System (GPS) is one of the synchronization solutions.
According to 3GPP specifications, the gNodeB clock must have high accuracy. The frequency
stability of a 10 MHz master clock of gNodeBs must be lower than ±0.05 ppm.
This frequency stability requirement must be met if a GPS clock is used as the clock source.
The clock signals are processed and synchronized as follows:

The GPS antenna system receives GPS signals at 1575.42 MHz and transmits the signals to
the GPS satellite card. The system can simultaneously trace up to eight (normally three or
four) satellites. The GPS satellite card processes the signals and transmits them to the master
clock module.
gNodeBs must be equipped with a GPS or RGPS receive device to support the GPS or RGPS
clock.
Benefits
This feature uses the GPS clock as a synchronization source. The gNodeB internal clock can
be synchronized with the transport network. No auxiliary clock equipment is required, which
reduces costs. The synchronized clock is of the required accuracy to meet both radio
frequency and transport network requirements.
4.5.3 Synchronization with BeiDou

Description
BeiDou satellite navigation system is a global satellite navigation system, which provides
all-time, round-the-clock high-precision positioning, navigation, and timing services for users
on the Earth's surface and in the terrestrial space.
In this feature, the gNodeB uses the BeiDou satellite navigation system as the clock source,
implementing frequency synchronization and time synchronization.
The gNodeB connects to the BeiDou satellite antenna system through the UMPTe board that
is configured with a BeiDou satellite card, thereby obtaining synchronization signals from the
synchronous satellite system.
The figure below shows the BeiDou synchronization solution.

Figure 4-4 BeiDou synchronization solution
gNodeBs must be equipped with a UMPTe that is configured with a BeiDou satellite card or a
UMPTg, as well as the BeiDou satellite antenna system.
Benefits
This feature provides another satellite clock synchronization mode in addition to GPS clock
synchronization.
This feature supports the backup of GPS clock synchronization and BeiDou synchronization,
thereby improving clock reliability.
4.5.4 Synchronization with Galileo

Description
Galileo satellite navigation system (Galileo) is a global satellite navigation system, which
provides all-time, round-the-clock high-precision positioning, navigation, and timing services
for users on the Earth's surface and in the terrestrial space.
In this feature, the gNodeB uses the Galileo as the clock source, implementing frequency
synchronization and time synchronization.
gNodeBs can connect to the external Galileo antenna system through the USCU equipped
with Galileo satellite cards, in order to obtain synchronization signals from the satellite
synchronization system.
The figure below shows the Galileo synchronization networking solution.

Figure 4-5 Galileo synchronization networking solution
Benefits
This feature provides another satellite clock synchronization mode in addition to GPS clock
synchronization.
This feature supports the backup of GPS clock synchronization and Galileo clock
synchronization, thereby improving clock reliability.
4.5.5 Synchronization with 1PPS+TOD

Description
gNodeBs can work with diversified clock sources to suit different clock topologies. This
feature uses the 1PPS clock as a synchronization source.
This feature is not applicable to integrated micro base stations.
1PPS+TOD signals are transmitted through cables within a short transmission distance.
Therefore, the transmission equipment or clock devices that can provide 1PPS+TOD signals
must be located near gNodeBs.
gNodeBs must be configured with a USCUb or UMPT board to support the 1PPS+TOD
clock.
Benefits
This feature uses the 1PPS clock as a synchronization source. The gNodeB internal clock can
be synchronized with the transport network. No auxiliary clock equipment is required, which

4.5.6 BITS Clock Synchronization

Description
gNodeBs can work with diversified clock sources to suit different clock topologies. This
feature uses the BITS as a synchronization source.
The BITS clock applies mainly to fixed network synchronization. It is a dedicated timing
signal generator used within a communications building or area. The BITS clock can be used
at any level in a digital synchronization network.
BITS clocks are layered according to the clock quality level to form a hierarchical clock
synchronization network through the transmission link in master/slave synchronization mode.
If the BITS clock is used as the high-accuracy reference clock for gNodeBs, the frequency
accuracy of the clock must meet the accuracy requirements for the SSU level.
If gNodeBs use the BITS clock to support frequency synchronization, they must be
configured with a USCU board. BITS ports on Huawei gNodeBs comply with the
requirements for 2048 kHz synchronization interface (75 ohms) defined in ITU-T G.703.
A BITS device is equipped with a high-accuracy local clock and uses a highly-reliable phase
lock algorithm. Therefore, the stable phase and excellent accuracy of clock signals are
provided for gNodeBs during the upper-level reference clock recovery from unavailability.
BITS signals are transmitted through cables within a short distance. Therefore, BITS
synchronization applies to the sites that are easy to obtain BITS signals. For example, if
transport equipment supporting BITS signal output and a gNodeB are deployed in the same
telecommunications room, the gNodeB can synchronize with the BITS clock.
Benefits
This feature uses the BITS as a synchronization source. The gNodeB internal clock can be
synchronized with the transport network. No auxiliary clock equipment is required, which
4.5.7 E1/T1 Clock Synchronization

Description
gNodeBs can work in multiple clock synchronization modes to suit different clock topologies.
E1/T1 is one of the synchronization solutions.
stability of a 10 MHz master clock of the gNodeB should be lower than ±0.05 ppm.
The gNodeB clock can be synchronized with the E1/T1 line clock source.
Benefits
This feature uses the E1/T1 clock as a synchronization source. The internal clock of the
gNodeB can be synchronized with the transmission network and no auxiliary clock equipment

is needed to reduce the costs. The synchronized clock can meet the accuracy requirements and
meet the radio frequency and transmission network requirements.
4.5.8 Clock Out-of-Synchronization Detection

Description
TDD has strict requirements for clock synchronization. If a base station becomes
asynchronized, the downlink transmission of the asynchronized base station may cause
interference to the uplink transmission of other synchronized base stations. The downlink
transmission of synchronized base stations may also cause interference to the uplink
transmission of the asynchronized base stations. When the interference is severe, UEs may
fail to access the network or have poor service experience. For example, service drops,
handover failures, or service failures are likely to occur.
This feature helps quickly and accurately identify asynchronized base stations, improving the
efficiency in base station asynchronization troubleshooting. With this feature, clock
out-of-synchronization detection can be triggered based on interference detection results, as
long as the interference is caused by clock asynchronization. Joint detection can be further
performed between base stations to identify the asynchronized base station. An alarm is then
reported to alert operators to base station asynchronization.
This feature is recommended for base stations operating on the same frequency and providing
continuous coverage when one asynchronized base station causes interference to other
synchronized or an asynchronized base station is interfered, and the asynchronized base
station cannot be identified.
Benefits
This feature helps quickly identify asynchronized base stations, facilitating the elimination of
interference caused by base station asynchronization.
4.5.9 Network-wide Synchronization Deviation Detection

Description
NR TDD has strict requirements for clock synchronization. If synchronization faults are not
diagnosed in time, interference may occur at a large scale. An out-of-synchronization base
station causes service deterioration of dozens of neighboring base stations. When the
interference is severe, UEs may fail to access the network, or receive a poor service
experience. For example, service drops or handover failures are likely to occur.
When multiple base stations have synchronization issues at the same time, the information
about a single base station or base stations in a small area may be insufficient for quickly
determining the base stations with synchronization issues. As shown in Figure 4-6, most of
the base stations in a small area have synchronization deviations, and only few of them are
synchronized. Under these circumstances, it is difficult to determine which type of base
stations have synchronization issues.

Figure 4-6 Synchronization deviation
To accurately identify base stations with synchronization deviations, sufficient reference base
stations are required for comparison. This function allows the inter-site synchronization
deviation detection among all gNodeBs managed by the same OSS. The inter-site
synchronization deviation data on the entire network is intelligently analyzed on the OSS, and
the few base stations with synchronization deviations are identified by using the majority of
base stations as reference base stations. Inter-site synchronization deviation is quantitatively
identified through sequence detection. If base stations properly receive the characteristic
sequence from each other, the bidirectional air interface delay between the base stations can
be measured to calculate the deviation.
Benefits
This function does not directly produce network performance gains. However, it helps
identify base stations with synchronization deviations, which reduces service costs.
4.6 FBFD-010022 Active/Standby IP Routes

Availability
Summary
When an active IP route becomes faulty, the standby IP route can take over, thereby
improving reliability of IP routes.
Benefits
This feature improves the reliability of the IP layer.
Description
This feature improves the reliability of the IP layer.
Users can configure two routes with the same destination IP address but different next-hop
addresses and priorities. The route with the higher priority is usually active. When this route

fails and stops working (for example, identified by ping operations), the route with the lower
priority takes over and starts working.
Enhancement
None
Dependency
 Hardware
The peer device must support this feature.
 UE
None
 Core network
None
 Other NEs
None
 Other features
This feature partially supports IPv6. IPv6 is not supported for BFD-based active and
standby routes.
4.7 FBFD-010023 Security Mechanism

Availability
Summary
This feature protects the network access security of devices. It covers the following functions:
Public Key Infrastructure (PKI), PKI redundancy, integrated firewall, access control based on
802.1X, and Anti-DDoS Attack over the Air Interface.
Benefits
This feature provides basic security capabilities for base stations to access the network.
Enhancement
 5G RAN3.0
This feature supports TLS1.3. TLS1.3 (RFC 8446) was officially published in August
2018. TLS1.3 features lower latency and higher security compared with TLS protocols
of earlier versions. Only one round trip time (RTT) is required for establishing a TLS1.3
connection, whereas 2-RTT is required in earlier versions. In TLS1.3, insecure/legacy
cipher suites RC4/CBC/RSA/SHA1 are deleted, and only AEAD cipher suites are
supported.
 5G RAN3.1
This feature supports DTLS over SCTP and Anti-DDoS Attack over the Air Interface.

Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
The PKI function requires that a PKI server be deployed on the operator's network.
The PKI redundancy function requires that a pair of active and standby PKI servers be
deployed on the operator's network.
Access control based on 802.1X requires that the peer access device of the base station
support IEEE 802.1X and an IEEE 802.1X-based authentication server be deployed on
the operator's network.
OSS: Huawei iManager U2020 is required.
 Other features
None
4.7.1 PKI
Description
PKI provides digital certificate management for NEs. It supports certificate authentication for
the IPsec tunnel between a base station and a security gateway (SeGW), or for the SSL
connection between a base station and the OMC.
Digital certificate management includes certificate creation, storage, distribution, and
revocation, and certificate revocation list (CRL) issuance.
Generally, a PKI system consists of a Certificate Authority (CA), a certificate repository (CR),
a CRL server, and the users to be authenticated.
Before delivery, a base station can be preconfigured with Huawei certificates whose format
complies with X.509 V3. After the base station starts operating, it can apply for the operator's
certificates from the PKI system and replace Huawei certificates.
Benefits
This function provides digital certificate authentication between two NEs to improve network
security.
4.7.2 gNodeB Supporting PKI Redundancy

Description
The PKI redundancy function requires that a pair of active and standby PKI servers be
deployed on the network and certificate management data be synchronized between the active
and standby PKI servers. If a session between a base station and the active PKI server fails,
the base station automatically re-initiates a session with the standby PKI server to continue to
apply for and update a certificate and obtain a CRL.

Benefits
Active and standby PKI servers are deployed on the network. When the active PKI server is
faulty, the base station automatically re-initiates a session with the standby PKI server to
continue to apply for and update a certificate and obtain a CRL. This prevents link faults
caused by certificate problems and improves PKI networking reliability.
4.7.3 Integrated Firewall

Description
Base stations support Access Control List (ACL). A base station uses ACL rules to perform
packet filtering based on packet attributes, such as the source IP address, destination IP
address, source port number, and destination port number. ACL rules can also be based on the
type of service (TOS), differentiated services code point (DSCP), and address wildcard.
If IPsec is enabled on the network, you can select the data flows that need to be encrypted and
authenticated by IPsec based on ACL rules.
Benefits
The base station filters packets based on ACL rules to prevent network attacks.
The base station identifies the packets that need to be encrypted and authenticated by IPsec
based on ACL rules.
4.7.4 Access Control Based on 802.1X

Description
IEEE 802.1X (port-based network access control) uses the physical access characteristics of
IEEE 802 LAN devices to provide a means of authenticating and authorizing devices attached
to a LAN port, and preventing access to that port when the authentication or authorization
fails.
The authentication and authorization of IEEE 802.1X use the framework of Extensible
Authentication Protocol (EAP). Before the authentication and authorization succeed, only
Extensible Authentication Protocol over LAN (EAPoL) packets can pass through the LAN
switch. All other packets will be dropped by the LAN switch.
Benefits
This function provides digital certificate authentication between a base station and the LAN
switch to improve network security.
4.7.5 DTLS over SCTP

Availability

Summary
Datagram Transport Layer Security (DTLS) over SCTP provides security protection for
signaling over the N2/Xn-C interfaces.
Benefits
1. This feature meets security requirements of customers.
2. This feature complies with 3GPP specifications and improves transmission security
competitiveness.
Description
DTLS ensures secure communication between the application layer and network layer. As
required by 3GPP TS 33.501 V15.1.0 "Security architecture and procedures for 5G system",
base stations provide security protection for signaling over the N2/Xn-C interfaces using
DTLS. Only DTLS1.2 is supported. For details, see RFC 6347.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
This feature requires that the core network support DTLS.
 Other NEs
None
 Other features
None
4.7.6 Anti-DDoS Attack over the Air Interface

Description
If the number of RRC connection setup requests, RRC connection reestablishment requests,
or RRC connection resume requests exceeds the preset thresholds, the base station regards the
UE as an attacker, rejects the UE's access requests, and implements a penalty period to
prohibit UE access, preventing a large number of signaling messages for UE access from
flooding into the base station.
Benefits
The anti-DDoS attack capability of the air interface is improved.

4.8 FBFD-010024 IP Performance Monitoring

Availability
Summary
This feature enhances the performance management function by providing an end-to-end
network monitoring mechanism, and collects the values of KPIs, including the traffic volume,
packet loss rate, delay, and jitter.
Benefits
 Convenient end-to-end network performance monitoring
 Enhanced system maintainability and testability
 Improved system performance
Description
IP performance monitoring (IPPM) is a Huawei-proprietary function. It provides end-to-end
network performance monitoring by enabling periodic packet exchanges. gNodeBs
periodically send packets to the peer devices, which respond to these packets. gNodeBs
acquire the KPIs, for example, the traffic volume, packet loss rate, delay, and jitter from the
response packets.
With these KPIs, operators can know the network quality and take necessary measures, such
as network optimization and capacity expansion.
IPPM can also be used for fault location. If the gNodeB and the peer equipment both have this
feature enabled, it is easy to determine whether the fault occurs on transmission network
devices or NR NEs. If every node on a network has IPPM enabled, faults can be quickly
located.
Enhancement
None
Dependency
 Hardware
The peer device must support this feature.
 UE
None
 Core network
None
 Other NEs
None
 Other features
Mutually exclusive features:

This feature does not support IPv6.
4.9 FBFD-021101 IPv4/IPv6 Dual Stack

Availability
Summary
This feature enables the S1-U, X2, Xn, and NG interfaces to use both the IPv6 and IPv4
transmission protocols. The S1-U interface connects a 5G base station and a 4G core network
(EPC) in 5G NSA networking. The NG interface connects a 5G base station and a 5G core
network in 5G SA networking. The X2 interface connects a 4G base station and a 5G base
station. The Xn interface connects a 5G base station and its adjacent 5G base station. All these
interfaces are based on the all-IP transmission protocol stack.
Benefits
This feature overcomes the problem that some NEs do not support IPv6 or evolution to IPv6
during IPv4-to-IPv6 evolution.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
The core network equipment must support IPv6.
 Other NEs
The transmission network must support IPv6.
 Other features
None
4.10 FBFD-010025 Basic O&M Package

Availability

Summary
This feature consists of local maintenance on the LMT, U2020 centralized management,
Secure Sockets Layer (SSL), software version upgrade management, hot patch management,
fault management, configuration management, performance management, and real-time
monitoring of system running information. This feature also supports security management,
environment monitoring, inventory management, license management, emergency license
control, antenna fault detection, remote electrical tilt control, and other related functions.
Benefits
This feature helps customers better implement network deployment, maintenance, and
optimization.
Enhancement
None
Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
The LMT requires a web browser, and the U2020 is deployed.
 Other features
None
4.10.1 Centralized U2020 Management

Description
In the network management center, Huawei U2020 provides telecom operators with Fault,
Configuration, Performance, Security, and Software (FCPSS) managements defined by 3GPP
to manage NEs on their subnets.
FCPSS managements include the following:
 Centralized fault management
 Centralized configuration management
 Centralized performance management
 Centralized security management
 Centralized software management

Benefits
Operators can manage all 5G NEs in the network management center, which effectively
reduces operating expense (OPEX).
4.10.2 Local Maintenance on the LMT

Description
This function is used for local maintenance of the gNodeB.
The local maintenance terminal (LMT) provides the following functions and tools:
 Execution of MML commands
 Query of alarms generated on the gNodeB
 Local gNodeB commissioning (when the transmission between the Huawei iManager
U2020 and the gNodeB is unavailable), such as software download and activation
 Local professional fault diagnosis of the gNodeB
Benefits
This function can be used for local maintenance of the gNodeB when centralized management
on the U2020 is unavailable, the transmission between the U2020 and the gNodeB is
unavailable, or onsite operations are required to handle a fault.
4.10.3 Software Version Upgrade Management

Description
gNodeB software management involves the following functions:
 Efficient and correct software installation and upgrade
− Automatic compatibility check of the software and hardware versions before
software installation and upgrade
− Automatic data conversion, which requires no manual configuration updates, before
software upgrade
− Software download based on configuration
This function reduces the software package size by 30% and shortens the download
time. It enables automatic software download for a new board in a gNodeB if no
software for the board has ever been downloaded to the gNodeB.
− Resumable download if the network connection recovers within 24 hour after
disconnection
There is no need to download the software from scratch.
− Automatic software download and activation for a batch of up to 1800 gNodeBs
− Simultaneous upgrade of hot patches and software using the software management
wizard of U2020
 Version management, for example, hardware and software version query
The procedure for upgrading gNodeB software includes the following steps:
 Download the software package from U2020 to the gNodeB.

The download process may take some time because of the limited bandwidth of the
operation and maintenance (OM) link, but this does not affect services.
 On the U2020 client, run the software activation command.
The gNodeB automatically loads the software onto the target boards and activates it. The
boards are then reset, and services on the boards are interrupted.
The two steps can be performed separately. For example, users can download the software
package in the daytime and activate the software at midnight. Performing these operations
separately helps reduce the risk of software upgrade failures and the impact of any potential
service interruptions.
Benefits
gNodeB software can be installed and upgraded and their versions can be managed efficiently
and correctly.
4.10.4 Hot Patch Management

Description
Hot patches are used to fix software bugs but do not interrupt ongoing services. Huawei
gNodeB hot patch management provides the following functions:
 Installing the hot patch
Two methods are supported to install the released hot patch package on the gNodeB:
− Run a single command to enable automatic download, loading, activation, and
confirmation of a hot patch.
− Run multiple commands in different steps to control each procedure of download,
loading, activation, and confirmation.
 Rolling back the latest hot patch
 Uninstalling the hot patch
Benefits
The gNodeB hot patches fix software bugs without interrupting ongoing services.
4.10.5 License Management

Description
This function involves gNodeB license control. A license file can be purchased from Huawei
and remotely downloaded and stored in a gNodeB. A license file determines whether optional
functions can be activated and how many optional functions can be activated. Operators can
manage and query the contents in a license file through the LMT or U2020 client.
Benefits
With this function, operators can purchase licenses for optional features to provide optimal
network performance.

4.10.6 Emergency License Control

Description
This function can be used to revoke license restrictions in emergencies so that operators can
handle a sudden network traffic increase. License restrictions can be revoked by running
MML commands on the LMT or U2020. In this way, the devices can be efficiently used and
the maximum hardware capacity of the devices can be reached. This function applies to
dynamic resource items.
For each R version, O&M personnel have three chances to revoke the license restrictions
through MML commands. The operation takes effect immediately after the commands are
executed. The validity period is seven days. After the three chances are used up, a new chance
can be obtained through software upgrades.
Benefits
This function helps operators handle a sudden traffic increase in situations such as sporting
events or holidays by increasing available radio network resources temporarily. In this way,
the capacity can be adjusted according to the actual usage, thereby saving the cost.
4.10.7 Fault Management

Description
Fault management involves fault detection, fault handling, fault correlation, and fault
reporting. With these functions, operators can identify network faults and take proper
measures to avoid service interruption.
 Fault detection
Fault detection includes physical and link layer environment monitoring, KPI alarm
monitoring, and other fault detection. A small number of faults may have a negative
impact on the traffic if self-testing, such as transport link loopback testing, is performed.
Some of these faults are detected automatically in the board startup phase, and some can
be manually triggered by executing fault testing commands.
Fault detection methods are properly designed to avoid false alarms and intermittent
alarms.
 Fault handling
The gNodeB isolates faults and automatically clears faults to minimize the impact on
services.
 Fault correlation
Fault management supports a run-time fault correlation mechanism. This mechanism
allows operators to be notified of the most important alarms (the root cause and impacts
on services) rather than all alarms when a fault occurs. The number of alarms greatly
decreases in this way, which makes it easier to locate and solve the network problems.
This mechanism can be predefined and embedded in the NEs. Operators can customize
alarm correlation handling rules on the MAE-Access.
 Fault reporting
Faults are reported to users in the form of alarms. With the alarm correlation function,
the report contains the correlation between alarms. If a correlative alarm for a fault
impacting services is reported, users can right-click the correlative alarm to check the
root alarm.

Operators can browse real-time alarm information, query historical alarm information, and
save alarm information. The online help provides detailed troubleshooting methods for each
type of alarms.
Benefits
This function provides automatic fault monitoring and handling of the gNodeB and enables
automatic fault monitoring of the equipment in NEs. With real-time alarm lists and alarm logs,
operators can have a comprehensive view of the network actual status at any time.
4.10.8 Configuration Management

Description
Configuration management helps telecom operators collect and manage the NE data, which
includes physical objects (equipment) and logical functions (such as cells and links). The
graphical user interface (GUI) makes the management easier.
To minimize the impact of reconfiguring a system, Huawei configuration management
provides the following functions:
 Modification on physical objects is independent of that on logical functions.
 All modifications for specific tasks are checked to ensure effectiveness before
application on the gNodeB.
 The consistency of configuration data between the NE and MAE-Access is ensured.
Both MAE-Deployment and MML configurations are supported.
 MAE-Deployment configuration
The MAE-Deployment provides powerful functions through wizards, templates, and
GUIs. It enables users to plan configuration items and check network data. This
facilitates data configuration for the entire radio access network. The MAE-Deployment
enables users to remotely create sites in batches, quickly expand network capacity, and
efficiently optimize their network. This improves the configuration efficiency and
accuracy.
 Using MML commands
All configuration data can be modified and queried by running MML commands.
Benefits
This function provides online and offline configuration functions and an overview of current
network status to implement rapid network deployment, capacity expansion, and network
reconfiguration.
4.10.9 Performance Management

Description
Performance measurement provides detailed information about a network to facilitate network
troubleshooting and optimization.
 Performance measurement management
This function enables telecom operators to manage available measurement.

For newly commissioned NE (gNodeB), the predefined performance measurement starts

after the initial startup. Performance measurement can be manually suspended and
resumed.
The NE (gNodeB) provides a man-machine interface. The MAE-Access can collect
necessary statistics and set related parameters, including measurement counters and
measurement periods.
The MAE-Access can obtain statistics in the binary format during each measurement
period. Result files can be stored on the NE for 3 x 24 hours. These files can be used
when data transmission fails. As a result, the MAE-Access can re-collect lost data.
 Performance measurement counters
Performance measurement counters include key counters and other counters. Key
counters are used to generate key performance indicators (KPIs) of a network. These
counters are defined on the MAE-Access and initialized when a gNodeB is started. The
MAE-Access supports addition, modification, and deletion of KPIs, related original
counters, and formulas. Measurement of other network performance counters can be
started as required.
 Real-time KPI monitoring
This function provides KPI monitoring and graphical display of network performance to
facilitate troubleshooting, drive testing, and network optimization. The minimum
sampling frequency is 10 seconds.
Benefits
Performance management effectively monitors network performance to complete network
troubleshooting and optimization. Real-time KPI monitoring is a more effective function that
helps users quickly locate performance-related issues.
4.10.10 Inventory Management

Description
Inventory management helps operators to query and manage the network assets on the
MAE-Access.
The objects which are managed by this function include physical objects (such as racks,
subracks, slots, boards, ports, and fans) and logical objects (such as software and patches).
When requested by the MAE-Access, an asset information file in .xml format is generated on
a gNodeB and is sent to the MAE-Access. The MAE-Access stores the received information
in the network inventory database.
The MAE-Access retrieves inventory information automatically from a gNodeB after gNodeB
commissioning and synchronizes inventory information with the gNodeB every day.
Benefits
Operators can obtain precise inventory data from the live network in a timely manner for
decision making.
Enhancement
None

Dependency
 Hardware
None
 UE
None
 Core network
None
 Other NEs
The LMT requires a web browser, and the MAE-Access is deployed.
 Other features
None
4.10.11 Energy Consumption Management

Description
Base stations periodically report the energy consumption data to the OSS. Through the OSS,
the changes in energy consumption of base stations can be monitored by operators, and an
energy consumption report can be exported for detailed analysis.
Bases station report three-level energy consumption data: base station level, BBU level, and
RF module level.
Benefits
Base stations report the energy consumption status to the OSS. Therefore, operators can
remotely monitor the energy consumption of base stations without the need to deploy
dedicated electricity meters. With the energy consumption report, operators can exactly know
the benefits provided by energy conservation.
After energy conservation and emission reduction functions are enabled for base stations,
operators can use the energy consumption management function to evaluate the energy-saving
effect.
4.11 FBFD-031003 PSU Intelligent Shutdown

Availability
Description
This feature enables certain power supply units (PSUs) to be powered on or off according to
the power consumption of a base station, reducing power consumption.

Benefits
Where there is light traffic, the base station can power off some PSUs to save power. If a base
station has three PSUs, enabling this feature when the traffic is light can reduce power
consumption by 4%–5%.
Enhancement
None
Dependency
 Hardware
This feature applies to macro base stations.
LampSite base stations do not support this feature.
 UE
None
 Core network
None
 Other NEs
None
 Other features
None

5G RAN3.1 Basic Feature Description 5 Acronyms and Abbreviations
5 Acronyms and Abbreviations
3GPP Third Generation Partnership Project
ABS Almost-blank subframe
ACK acknowledgment
ACL Access Control List
AES Advanced Encryption Standard
AFC Automatic Frequency Control
AH Authentication Header
AMBR Aggregate Maximum Bit Rate
AMC Adaptive Modulation and Coding
AMR Adaptive Multi-Rate
ANR Automatic Neighboring Relation
ARP Allocation/Retention Priority
ARQ Automatic Repeat Request
BCH Broadcast Channel
BCCH Broadcast Control Channel
BITS Building Integrated Timing Supply System
BLER Block Error Rate

CA Carrier aggregation
C/I Carrier-to-Interference Power Ratio
CC Component carrier
CCCH Common Control Channel
CDMA Code Division Multiple Access
CEU Cell Edge Users
CGI Cell Group Indicator
CME Configuration Management Express
CP Cyclic Prefix
CPICH Common Pilot Channel
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
CRS Cell-specific reference signal
CSI-RS Channel state information reference signal
DCCH Dedicated Control Channel
DES Data Encryption Standard
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services
DL-SCH Downlink Shared Channel
DRB Data Radio Bearer
DRX Discontinuous Reception
DSCP DiffServ Code Point
DTCH Dedicated Traffic Channel
ECM EPS Control Management
eCSFB Enhanced CS Fallback
EDF Early Deadline First

EF Expedited Forwarding
eHRPD Evolved high rate packet data
eICIC Enhanced Inter-cell Interference Coordination
eMBMS evolved Multimedia Broadcast Multimedia System
EMM EPS Mobility Management
EMS Element Management System
eNodeB evolved NodeB
EPC Evolved Packet Core
EPS Evolved Packet System
ESP Encapsulation Security Payload
ETWS Earthquake and Tsunami Warning System
E-UTRA Evolved –Universal Terrestrial Radio Access
FCPSS Fault, Configuration, Performance, Security and Software Managements
FDD Frequency Division Duplex
FEC Forward Error Correction
FTP File Transfer Protocol
GBR Guaranteed Bit Rate
GERAN GSM/EDGE Radio Access Network
GPS Global Positioning System
HARQ Hybrid Automatic Repeat Request
HII High Interference Indicator
HMAC Hash Message Authentication Code
HMAC_MD5 HMAC Message Digest 5
HMAC_SHA HMAC Secure Hash Algorithm
HO Handover

HRPD High Rate Packet Data
ICIC Inter-cell Interference Coordination
IKEV Internet Key Exchange Version
IMS IP Multimedia Service
IP PM IP Performance Monitoring
IPsec IP Security
IRC Interference Rejection Combining
KPI Key Performance Indicator
LMT Local Maintenance Terminal
MAC Medium Admission Control
MIB Master Information Block
MCH Multicast Channel
MCCH Multicast Control Channel
MCS Modulation and Coding Scheme
MIMO Multiple Input Multiple Output
min_GBR Minimum Guaranteed Bit Rate
MME Mobility Management Entity
MML Man-Machine Language
MOS Mean Opinion Score
MRC Maximum-Ratio Combining
MTCH Multicast Traffic Channel
MU-MIMO Multiple User-MIMO

NACC Network Assisted Cell Changed
NACK Non acknowledgment
NAS Non-Access Stratum
NRT Neighboring Relation Table
OCXO Oven Controlled Crystal Oscillator
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiplexing Access
OI Overload Indicator
OMC Operation and Maintenance Center
OOK On-Off-Keying
PBCH Physical Broadcast Channel
PCCH Paging Control Channel
PCFICH Physical Control Format Indicator Channel
PCH Paging Channel
PCI Physical Cell Identity
PDB Packet Delay Budget
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDH Plesiochronous Digital Hierarchy
PDSCH Physical Downlink Shared Channel
PF Proportional Fair
PHB Per-Hop Behavior
PHICH Physical Hybrid ARQ Indicator Channel
PM Performance Measurement
PLMN Public Land Mobile Network
PMCH Physical Multicast Channel

PRACH Physical Random Access Channel
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RA Random Access
RACH Random Access Channel
RAM Random Access Memory
RAT Radio Access Technology
RB Resource Block
RCU Radio Control Unit
RET Remote Electrical Tilt
RF Radio Frequency
RLC Radio Link Control
RRC Radio Resource Control
RRM Radio Resource Management
RRU Remote Radio Unit
RS Reference Signal
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
RSSI Received Signal Strength Indicator
RTT Round Trip Time
RV Redundancy Version
Rx Receive

S1 interface between EPC and E-UTRAN
SBT Smart Bias Tee
SC-FDMA Single Carrier-Frequency Division Multiple Access
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SFBC Space Frequency Block Coding
SFP Small Form – factor Pluggable
SGW Serving Gateway
SIB System Information Block
SID Silence Indicator
SINR Signal to Interference plus Noise Ratio
SRB Signaling Radio Bearer
SRS Sounding Reference Signal
SSL Security Socket Layer
STBC Space Time Block Coding
STMA Smart TMA
TAC Transport Admission Control
TCP Transmission Control Protocol
TDD Time Division Duplex
TMA Tower Mounted Amplifier
TMF Traced Message Files
ToS Type of Service
TTI Transmission Time Interval
Tx Transmission
UE User Equipment
UL-SCH Uplink Shared Channel

USB Universal Serial Bus
U2020 Huawei OMC
VLAN Virtual Local Area Network
VoIP Voice over IP
WRR Weighted Round Robin
X2 interface among eNodeBs

5G RAN3.1 Basic Feature Description 6 Appendix
6 Appendix
6.1 Appendix 1: NR Spectrum List
6.1 Appendix 1: NR Spectrum List

Table 6-1 NR sub-3 GHz spectrum list
Band Uplink Downlink Duplex
Mode
n1 1920–1980 MHz 2110–2170 MHz FDD
n2 1850–1910 MHz 1930–1990 MHz FDD
n3 1710–1785 MHz 1805–1880 MHz FDD
n5 824–849 MHz 869–894 MHz FDD
n7 2500–2570 MHz 2620–2690 MHz FDD
n8 880–915 MHz 925–960 MHz FDD
n12 699–716 MHz 729–746 MHz FDD
n20 832–862 MHz 791–821 MHz FDD
n25 1850–1915 MHz 1930–1995 MHz FDD
n28 703–748 MHz 758–803 MHz FDD
n34 2010–2025 MHz 2010–2025 MHz TDD
n38 2570–2620 MHz 2570–2620 MHz TDD
n39 1880–1920 MHz 1880–1920 MHz TDD
n40 2300–2400 MHz 2300–2400 MHz TDD
n41 2496–2690 MHz 2496–2690 MHz TDD
n51 1427-1432 MHz 1427-1432 MHz TDD
n66 1710–1780 MHz 2110–2200 MHz FDD

5G RAN3.1 Basic Feature Description 6 Appendix
n70 1695–1710 MHz 1995–2020 MHz FDD

n71 663–698 MHz 617–652 MHz FDD
n77 3300–4200 MHz 3300–4200 MHz TDD
n78 3300–3800 MHz 3300–3800 MHz TDD
n79 4400–5000 MHz 4400–5000 MHz TDD
Table 6-2 Sub-3 GHz spectrum list (SUL)
Band Duplex Mode and Frequency Band

n80 SUL: 1710–1785 MHz
n81 SUL: 880–915 MHz
n82 SUL: 832–862 MHz
n83 SUL: 703–748 MHz
n84 SUL: 1920–1980 MHz
n85 SUL: 2496–2690 MHz

5G RAN3.1 Basic Feature Description

Uploaded by

Document Information

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

5G RAN3.1 Basic Feature Description

Uploaded by

Copyright:

Available Formats

5G RAN3.

1 Basic Feature Description

5G RAN3.1 Basic Feature Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. i

1 Change History .............................................................................................................................. 1

3 RAN Architecture & Features ................................................................................................... 15

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. ii

3.5 FBFD-010011 Scheduling .......................................................................................................................................... 30

4 Transmission & Security ........................................................................................................... 50

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. iii

4.7 FBFD-010023 Security Mechanism ........................................................................................................................... 65

5 Acronyms and Abbreviations ................................................................................................... 79

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. iv

Issue Date Author Description

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 1

Issue Date Author Description

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 2

2.1 FBFD-010001 3GPP R15 Standards Compliance

2.1 FBFD-010001 3GPP R15 Standards Compliance

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 3

2.2 FBFD-010002 LDPC+Polar Codes

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 4

2.3 FBFD-010003 MIMO Basic Package

 Sub-3 GHz indicates frequency bands below 3 GHz.

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 5

multi-antenna reception. This improves the communications system coverage without

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 6

2.4 FBFD-010004 Basic Numerology

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 7

2.5 FBFD-010005 Self-contained Frame Structure

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 8

2.6 FBFD-020100 Slot Configuration

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 9

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 10

2.7 FBFD-010006 F-OFDM

Subcarrier Channel Bandwidth

30 95.4% 97.2% 97.65% 98.28%

Table 2-2 Maximum spectrum utilization of different mmWave channel bandwidths

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 11

2.8 FBFD-030101 NR FDD (Non Massive MIMO)

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 12

Module Frequency Band

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 13

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 14

3 RAN Architecture & Features

3.1 FBFD-010007 Scalable Bandwidth

3.1 FBFD-010007 Scalable Bandwidth

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 15

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 16

2100 MHz (n1):

3.2 FBFD-010008 Basic Modulation Schemes

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 17

3.3 FBFD-010009 Channel Management

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 18

3.3.1 Logical Channel Management

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 19

 The BCCH is mapped to the broadcast channel (BCH).

3.3.2 Transport Channel Management

Issue 01 (2020-05-08) Copyright © Huawei Technologies Co., Ltd. 20

 The RACH is mapped to the physical random access channel (PRACH).

3.3.3 Physical Channel Management