0% found this document useful (0 votes)
182 views67 pages

5G Networking and Signaling (5G RAN5.1 - 02)

Uploaded by

freveco111
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
182 views67 pages

5G Networking and Signaling (5G RAN5.1 - 02)

Uploaded by

freveco111
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 67

5G RAN

5G Networking and Signaling


Feature Parameter Description

Issue 02
Date 2021-04-30

HUAWEI TECHNOLOGIES CO., LTD.


Copyright © Huawei Technologies Co., Ltd. 2021. 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 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. i


5G RAN
5G Networking and Signaling Feature Parameter
Description Contents

Contents

1 Change History.........................................................................................................................1
1.1 5G RAN5.1 02 (2021-04-30)............................................................................................................................................... 1
1.2 5G RAN5.1 01 (2021-03-05)............................................................................................................................................... 2
1.3 5G RAN5.1 Draft B (2021-01-31)...................................................................................................................................... 2
1.4 5G RAN5.1 Draft A (2020-12-29)...................................................................................................................................... 2

2 About This Document.............................................................................................................4


2.1 General Statements................................................................................................................................................................ 4
2.2 Features in This Document.................................................................................................................................................. 4
2.3 Differences Between NR FDD and NR TDD................................................................................................................... 5
2.4 Differences Between NSA and SA..................................................................................................................................... 5
2.5 Differences Between High Frequency Bands and Low Frequency Bands............................................................ 5

3 Overview....................................................................................................................................7
4 Basic Signaling Procedures in SA Networking............................................................... 11
4.1 Principles.................................................................................................................................................................................. 12
4.1.1 System Information Broadcast......................................................................................................................................12
4.1.1.1 System Information Block........................................................................................................................................... 12
4.1.1.2 System Information Transmission............................................................................................................................ 14
4.1.1.3 System Information Acquisition................................................................................................................................ 16
4.1.2 Paging.................................................................................................................................................................................... 17
4.1.2.1 Triggering of Paging......................................................................................................................................................17
4.1.2.2 Paging Mechanism over the Air Interface............................................................................................................. 18
4.1.3 Random Access...................................................................................................................................................................20
4.1.3.1 RA Triggering Scenarios and RA Mechanisms......................................................................................................21
4.1.3.2 RA Procedures................................................................................................................................................................. 22
4.1.3.2.1 Contention-based RA Procedure........................................................................................................................... 22
4.1.3.2.2 Non-Contention-based RA Procedure................................................................................................................. 24
4.1.4 RRC Connection Management...................................................................................................................................... 26
4.1.4.1 RRC Connection Setup..................................................................................................................................................27
4.1.4.2 RRC Connection Reconfiguration............................................................................................................................. 28
4.1.4.3 RRC Connection Release.............................................................................................................................................. 29
4.1.4.4 RRC Connection Reestablishment............................................................................................................................ 29
4.1.4.5 Uplink Out-of-Synchronization Management..................................................................................................... 31

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. ii


5G RAN
5G Networking and Signaling Feature Parameter
Description Contents

4.1.4.6 UE Inactivity Management......................................................................................................................................... 32


4.1.5 Context Management...................................................................................................................................................... 32
4.1.5.1 Context Setup.................................................................................................................................................................. 32
4.1.5.2 Context Modification.................................................................................................................................................... 34
4.1.5.3 Context Release.............................................................................................................................................................. 35
4.1.6 PDU Session Management............................................................................................................................................. 36
4.1.6.1 PDU Session Setup.........................................................................................................................................................37
4.1.6.2 PDU Session Modification........................................................................................................................................... 37
4.1.6.3 PDU Session Release..................................................................................................................................................... 38
4.2 Network Analysis.................................................................................................................................................................. 39
4.2.1 Benefits................................................................................................................................................................................. 40
4.2.2 Impacts.................................................................................................................................................................................. 40
4.3 Requirements......................................................................................................................................................................... 40
4.3.1 Licenses................................................................................................................................................................................. 40
4.3.2 Software................................................................................................................................................................................40
4.3.3 Hardware.............................................................................................................................................................................. 41
4.4 Operation and Maintenance............................................................................................................................................. 42

5 Basic Signaling Procedures in NSA Networking............................................................ 43


5.1 Principles.................................................................................................................................................................................. 44
5.1.1 System Information Broadcast......................................................................................................................................44
5.1.2 Paging.................................................................................................................................................................................... 45
5.1.3 RA to the eNodeB..............................................................................................................................................................45
5.1.4 Signaling Connection Management............................................................................................................................45
5.1.5 E-UTRAN Radio Bearer Management........................................................................................................................ 45
5.1.6 NR B1 Measurement........................................................................................................................................................ 45
5.1.7 NG-RAN Radio Bearer Management.......................................................................................................................... 46
5.1.7.1 DRB Setup......................................................................................................................................................................... 47
5.1.7.2 DRB Modification........................................................................................................................................................... 48
5.1.7.3 DRB Release..................................................................................................................................................................... 48
5.1.8 RA to the gNodeB............................................................................................................................................................. 50
5.1.8.1 RA Triggering Scenarios and RA Mechanisms......................................................................................................50
5.1.8.2 RA Procedures................................................................................................................................................................. 51
5.1.8.2.1 Contention-based RA Procedure........................................................................................................................... 51
5.1.8.2.2 Non-Contention-based RA Procedure................................................................................................................. 52
5.1.8.3 RA Optimization............................................................................................................................................................. 54
5.2 Network Analysis.................................................................................................................................................................. 56
5.2.1 Benefits................................................................................................................................................................................. 56
5.2.2 Impacts.................................................................................................................................................................................. 56
5.3 Requirements......................................................................................................................................................................... 57
5.3.1 Licenses................................................................................................................................................................................. 57
5.3.2 Software................................................................................................................................................................................57
5.3.3 Hardware.............................................................................................................................................................................. 58

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. iii


5G RAN
5G Networking and Signaling Feature Parameter
Description Contents

5.4 Operation and Maintenance............................................................................................................................................. 58

6 Parameters.............................................................................................................................. 59
7 Counters.................................................................................................................................. 60
8 Glossary................................................................................................................................... 61
9 Reference Documents...........................................................................................................62

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. iv


5G RAN
5G Networking and Signaling Feature Parameter
Description 1 Change History

1 Change History

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


"Glossary", and "Reference Documents" chapters. These changes include:
● Technical Changes
Changes in functions and their corresponding parameters
● Editorial Changes
Improvements or revisions to the documentation

1.1 5G RAN5.1 02 (2021-04-30)


This issue includes the following changes.

Technical Changes
Change Description Parameter RAT Base Station Model
Change

Added an impact None Low- 3900 and 5900 series


relationship with the frequenc base stations
low latency and high y TDD DBS3900 LampSite
reliability function. For and DBS5900
details, see 4.2.2 LampSite
Impacts and 5.2.2
Impacts.

None None High- 3900 and 5900 series


frequenc base stations
y TDD DBS3900 LampSite
and DBS5900
LampSite

None None FDD 3900 and 5900 series


base stations
DBS3900 LampSite
and DBS5900
LampSite

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 1


5G RAN
5G Networking and Signaling Feature Parameter
Description 1 Change History

Editorial Changes
Revised descriptions in this document.

1.2 5G RAN5.1 01 (2021-03-05)


This issue includes the following changes.

Technical Changes
Change Description Parameter RAT Base Station Model
Change

Added descriptions None Low- 3900 and 5900 series


about SIB8. For details, frequenc base stations
see 4.1.1.1 System y TDD DBS3900 LampSite
Information Block. High- and DBS5900
frequenc LampSite
y TDD
FDD

Editorial Changes
Revised descriptions in this document.

1.3 5G RAN5.1 Draft B (2021-01-31)


This issue includes the following changes.

Technical Changes
None

Editorial Changes
Revised descriptions in this document.

1.4 5G RAN5.1 Draft A (2020-12-29)


This issue introduces the following changes to 5G RAN3.1 02 (2020-07-03).

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 2


5G RAN
5G Networking and Signaling Feature Parameter
Description 1 Change History

Technical Changes
Change Description Parameter RAT Base Station Model
Change

Added support for SA None High- 3900 and 5900 series


networking in high- frequenc base stations
frequency FWA y TDD
scenarios. For details,
see 2.5 Differences
Between High
Frequency Bands and
Low Frequency
Bands.

Added a protection Added the Low- 3900 and 5900 series


measure against gNBConnStateTi frequenc base stations
exceptions that occur mer.SigUeNoNas y TDD DBS3900 LampSite
when UEs only have MsgTransTmr High- and DBS5900
signaling connections. parameter. frequenc LampSite
For details, see 4.1.5.3 y TDD
Context Release.

Removed the None Low- 3900 and 5900 series


configuration frequenc base stations
restrictions when both y TDD DBS3900 LampSite
the full-bandwidth and DBS5900
initial BWP switch and LampSite
power saving BWP
switch are turned on.
For details, see 4.2.2
Impacts.

Added the eXn None Low- 3900 and 5900 series


interface. For details, frequenc base stations
see 3 Overview. y TDD DBS3900 LampSite
High- and DBS5900
frequenc LampSite
y TDD
FDD

Editorial Changes
Revised descriptions in this document.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 3


5G RAN
5G Networking and Signaling Feature Parameter
Description 2 About This Document

2 About This Document

2.1 General Statements


Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE

This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.

2.2 Features in This Document


This document describes the following features.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 4


5G RAN
5G Networking and Signaling Feature Parameter
Description 2 About This Document

Feature ID Feature Name Chapter/Section

FBFD-021104 SA Option 2 Architecture 4 Basic Signaling Procedures in SA


Networking

2.3 Differences Between NR FDD and NR TDD


Function Difference Chapter/Section
Name

Basic None 4 Basic Signaling Procedures in SA


signaling Networking
procedures in
SA
networking

Basic None 5 Basic Signaling Procedures in NSA


signaling Networking
procedures in
NSA
networking

2.4 Differences Between NSA and SA


Function Difference Chapter/Section
Name

Basic This function is 4 Basic Signaling Procedures in SA


signaling supported only in SA Networking
procedures in networking.
SA
networking

Basic This function is 5 Basic Signaling Procedures in NSA


signaling supported only in NSA Networking
procedures in networking.
NSA
networking

2.5 Differences Between High Frequency Bands and


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

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 5


5G RAN
5G Networking and Signaling Feature Parameter
Description 2 About This Document

Function Difference Chapter/Section


Name

Basic This function is 4 Basic Signaling Procedures in SA


signaling supported in both high Networking
procedures in and low frequency
SA bands, with the
networking following differences:
● SA networking is
supported only in
FWA scenarios in
high frequency bands
and is supported in
all scenarios in low
frequency bands.
● Allocation of
dedicated physical
random access
channel (PRACH)
resources by gNodeB
for other system
information (OSI) is
supported only in low
frequency bands.
● RRC_INACTIVE state
is supported only in
low frequency bands.

Basic Optimized counter 5 Basic Signaling Procedures in NSA


signaling measurement for Networking
procedures in contention-based RA:
NSA This function is
networking supported only in low
frequency bands.
Other functions: None

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 6


5G RAN
5G Networking and Signaling Feature Parameter
Description 3 Overview

3 Overview

5G networking modes include standalone (SA) and non-standalone (NSA), as


defined in section 7.2 "5G Architecture Options" of 3GPP TR 38.801 V14.0.0.
Huawei supports SA networking, NSA networking, and NSA and SA hybrid
networking.

SA Networking
In SA networking, gNodeBs or enhanced 4G base stations (referred to as eLTE
eNodeBs) are connected to the 5G Core Network (5GC) in a standalone mode. It
is the target networking of 5G network development. For details about eLTE
eNodeBs, see section 3.1 "Definitions" in 3GPP TR 38.801 V14.0.0.

Figure 3-1 shows the SA networking architectures.

Figure 3-1 SA networking architectures

Huawei SA networking uses the Option 2 architecture. Option 2 is an end-to-end


5G network architecture, in which the UEs, new radio, and core network all adopt
5G standards. Option 2 includes the 5GC, gNodeB, and UE. Each NE is as follows:

● 5GC: consists of the access and mobility management function (AMF) and the
user plane function (UPF). AMF provides UE access permission and mobility
management, while UPF provides user plane management.
● gNodeB: consists of a baseband processing unit, radio equipment, and
antenna. It is used for transmitting service data and signaling.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 7


5G RAN
5G Networking and Signaling Feature Parameter
Description 3 Overview

● UE: indicates the 5G terminal.


5GC connects to the gNodeBs through the NG interface. The gNodeBs connect to
each other through the Xn interface, and to the UEs through the Uu interface.
Each interface is as follows:
● NG interface: consists of NG-C and NG-U interfaces, which implement NG
control plane functions and NG user plane functions, respectively.
● Xn interface: consists of Xn-C and Xn-U interfaces, which implement Xn
control plane functions and Xn user plane functions, respectively.
● eXn interface: consists of eXn-C and eXn-U interfaces, which implement eXn
control plane functions and eXn user plane functions, respectively. For more
details, see eXn Self-Management.
● Uu interface: consists of Uu-C and Uu-U interfaces, which implement Uu
control plane functions and Uu user plane functions, respectively.
For details about the basic signaling procedures in SA networking, see 4 Basic
Signaling Procedures in SA Networking.

NSA Networking
In NSA networking, 5G networks are built on and integrated with 4G networks.
Signals are transmitted using radio resources from both eNodeBs and gNodeBs.
Such an approach can help 5G fast commercial use.
Figure 3-2 shows the NSA networking architectures.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 8


5G RAN
5G Networking and Signaling Feature Parameter
Description 3 Overview

Figure 3-2 NSA networking architectures

Huawei NSA networking uses the Option 3 and Option 3x architectures. In both
architectures, the eNodeB serves as the control plane anchor to carry control plane
data. The difference is as follows:
● In Option 3, the eNodeB is the data split anchor. The eNodeB distributes some
of the user plane data to the gNodeB, and still carries the remaining user
plane data.
● In Option 3x, the gNodeB is the data split anchor. The gNodeB distributes
some of the user plane data to the eNodeB, and still carries the remaining
user plane data.
Option 3 and Option 3x architectures include EPC, eNodeB, gNodeB, and UE. Each
NE is as follows:
● EPC: indicates the 4G core network, which provides mobility management and
user plane management.
● eNodeB: functions as the master eNodeB (MeNB) in Option 3 and Option 3x.
● gNodeB: functions as the secondary gNodeB (SgNB) in Option 3 and Option
3x.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 9


5G RAN
5G Networking and Signaling Feature Parameter
Description 3 Overview

● UE: indicates a terminal capable of E-UTRA-NR dual connectivity (EN-DC).


The UE maintains DC with the eNodeB and the gNodeB, and uses radio
resources from both base stations for transmission.

The EPC connects to the eNodeB or the gNodeB through the S1 interface. The
eNodeB and the gNodeB connect through the X2 interface. The gNodeB connects
to the UE through the Uu interface. Each interface is as follows:

● S1 interface: consists of S1-C and S1-U interfaces, which implement S1 control


plane functions and S1 user plane functions, respectively.
● X2 interface: consists of X2-C and X2-U interfaces, which implement X2
control plane functions and X2 user plane functions, respectively.
● Uu interface: consists of Uu-C and Uu-U interfaces, which implement Uu
control plane functions and Uu user plane functions, respectively.

For details about the basic signaling procedures in NSA networking, see 5 Basic
Signaling Procedures in NSA Networking.

NSA and SA Hybrid Networking


Due to high costs of direct SA networking deployment, Huawei provides NSA and
SA hybrid networking to support smooth evolution from NSA networking to SA
networking. Figure 3-3 shows the NSA and SA hybrid networking architectures.

Figure 3-3 NSA and SA hybrid networking architectures

Huawei NSA and SA hybrid networking uses the Option 3 and Option 2 hybrid
architecture and the Option 3x and Option 2 hybrid architecture.

For details about the Option 3 and Option 3x architectures, see NSA Networking.
For details about the Option 2 architecture, see SA Networking.

The NR-capable UE 1 accesses the network in SA networking. For details about


the related signaling procedure, see 4 Basic Signaling Procedures in SA
Networking.

The EN-DC-capable UE 2 maintains DC with the eNodeB and the gNodeB, and
accesses the network in NSA networking. For details about the related signaling
procedure, see 5 Basic Signaling Procedures in NSA Networking.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 10


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

4 Basic Signaling Procedures in SA


Networking

Figure 4-1 shows the basic signaling procedures in SA networking.

Figure 4-1 Basic signaling procedures in SA networking

Basic signaling procedures in SA networking include:

1. System information broadcast


System information broadcast is the first step for a UE to obtain the basic
network service information. Through the system information broadcast
procedure, the UE can obtain the basic access stratum (AS) and non-access
stratum (NAS) information. For details about system information broadcast,
see 4.1.1 System Information Broadcast.
2. (Optional) Paging
When the network needs to set up a connection with a UE, it initiates a
paging procedure to locate the UE. This procedure involves only the

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 11


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

terminating UE, not the originating UE. For details about the paging
procedure, see 4.1.2 Paging.
3. Random access (RA)
RA starts when a UE sends an RA preamble and ends when an RRC
connection is set up between the UE and the network. For details about RA,
see 4.1.3 Random Access.
4. RRC connection management
RRC connection management includes RRC connection setup, reconfiguration,
release, and reestablishment between a UE and a gNodeB, as well as uplink
out-of-synchronization management and UE inactivity management. For
details about RRC connection management, see 4.1.4 RRC Connection
Management.
5. Context management
After an RRC connection is set up, the gNodeB sends an INITIAL UE MESSAGE
to the 5GC to trigger the NG-C connection setup and receive the UE context.
Context management includes UE context setup, modification, and release.
For details about context management, see 4.1.5 Context Management.
6. PDU session management
A PDU session is a data connection between a UE and a data network (DN).
PDU session management includes PDU session setup, modification, and
release. For details about PDU session management, see 4.1.6 PDU Session
Management.

4.1 Principles

4.1.1 System Information Broadcast


System information broadcast is the first step for a UE to obtain the basic network
service information. In this procedure, the gNodeB transmits system information
and the UE obtains system information.

● The content of system information broadcast is carried in system information


blocks (SIBs). For details about SIBs, see 4.1.1.1 System Information Block.
● For details about how the gNodeB transmits system information, see 4.1.1.2
System Information Transmission.
● For details about how a UE receives system information, see 4.1.1.3 System
Information Acquisition.

4.1.1.1 System Information Block


According to section 7.3 "System Information Handling" of 3GPP TS 38.300
V15.5.0, system information can be classified into minimum system information
(MSI) and other system information (OSI) by content.

● MSI includes the master information block (MIB) and system information
block 1 (SIB1). The MIB provides the information used to capture SIB1, and
SIB1 provides basic information required for cell selection when a UE initially
accesses the network.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 12


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

● OSI includes SIB2 to SIBn. It provides information such as the mobility, time,
earthquake and tsunami warning system (ETWS), and commercial mobile
alert system (CMAS) for a UE. The current version supports only SIB2, SIB3,
SIB4, SIB5, SIB8, and SIB9.

The MIB and each SIB contain different information, as listed in Table 4-1. For
details, see sections 6.2.2 "Message definitions" and 6.3.1 "System information
blocks" of 3GPP TS 38.331 V15.5.0.

Table 4-1 Contents of the MIB and SIBs

Categor Informati Content


y on Type

MSI MIB System frame number (SFN) and information used to


capture SIB1

SIB1 Operator information of the cell, initial bandwidth part


(BWP) informationa, and scheduling information of other
SIBs

OSI SIB2 Common information required for intra-frequency cell


reselection, inter-frequency cell reselection, and inter-RAT
cell reselection

SIB3 Intra-frequency cell reselection parameters and intra-


frequency cell blacklist

SIB4 Non-serving frequency reselection parameters, inter-


frequency cell reselection parameters, and inter-
frequency cell blacklist

SIB5 Inter-RAT frequency reselection parameters, inter-RAT


cell reselection parameters, and inter-RAT cell blacklist

SIB8 CMAS warning notification

SIB9 Coordinated Universal Time (UTC), Global Positioning


System (GPS) time, and local time

a: In SA networking, the initial BWP information is carried in the


locationAndBandwidth field of the initialDownlinkBWP and initialUplinkBWP IEs
in SIB1. The initial BWP is controlled by the INIT_BWP_FULL_BW_SW option
(selected by default) of the NRDUCellAlgoSwitch.BwpConfigPolicySwitch
parameter. Changing the setting of this option will cause the cell to restart,
affecting admitted UEs.
● When this option is selected, the gNodeB configures the full-bandwidth
initial BWP for all UEs.
● When this option is deselected, the gNodeB configures an initial BWP with
the bandwidth specified by CORESET#0 for all UEs. UEs cannot use the full
bandwidth during access, affecting the UE access success rate. In addition,
PUCCH and PRACH resources in the initial BWP divide PUSCH resources in
the frequency domain, affecting the uplink cell throughput. For details about
CORESET#0, see section 6.3.2 "Radio resource control information elements"
of 3GPP TS 38.331 V15.5.0.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 13


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

4.1.1.2 System Information Transmission


Figure 4-2 shows the system information transmission path.

● MIB: BCCH (broadcast control channel, a logical channel) -> BCH (broadcast
channel, a transport channel) -> PBCH (physical broadcast channel, a physical
channel)
● SIB1: BCCH (a logical channel) -> DL-SCH (downlink shared channel, a
transport channel) -> PDSCH (physical downlink shared channel, a physical
channel)
● OSI: BCCH (a logical channel) -> DL-SCH (a transport channel) -> PDSCH (a
physical channel) (For OSI, multiple SIBs with the same scheduling period are
encapsulated into one SI message for transmission.)

Figure 4-2 System information transmission path

Figure 4-3 shows system information broadcast, where:

● MIB: broadcast by the gNodeB periodically. Within a scheduling period of 80


ms, the MIB can be repeatedly transmitted based on the broadcast period
specified by NRDUCell.SsbPeriod.
● SIB1: broadcast by the gNodeB periodically. Within a scheduling period of 160
ms, SIB1 can be repeatedly transmitted based on the broadcast period
specified by NRDUCell.Sib1Period.
● OSI: broadcast periodically by the gNodeB (without repetition in a scheduling
period), or broadcast by the gNodeB after a UE initiates a subscription

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 14


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

request. The broadcast mode and broadcast period can be configured


independently for different types of OSI.
– The system information type is specified by the gNBSibConfig.SibType
parameter.
– The broadcast mode is specified by the gNBSibConfig.SibTransPolicy
parameter.
– The broadcast period is specified by the gNBSibConfig.SibTransPeriod
parameter.
In addition, the NRDUCell.SibConfigId and gNBSibConfig.SibConfigId
parameters can be associated to specify the system information broadcast
mode and broadcast period used by a cell.

Figure 4-3 System information broadcast

System information may change during the running process. When system
information changes, the gNodeB performs the following operations:

1. The gNodeB sends a Short Message to the UE, indicating a system


information change.
The gNodeB sets the systemInfoModification field in the Short Message to 1.
For details, see section 6.5 "Short Message" in 3GPP TS 38.331 V15.5.0.
2. The gNodeB sends the changed system information in the next BCCH
modification period.
The gNodeB changes the valueTag value of the corresponding system
information in SIB1, and sends the changed system information to the UE in
the next BCCH modification period.

As described in section 6.3.2 "Radio resource control information elements" of


3GPP TS 38.331 V15.5.0, the system information update process is performed
within specific radio frames, which are referred to as the BCCH modification period
(m radio frames).

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 15


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

The BCCH modification period is equal to modificationPeriodCoeff multiplied by


defaultPagingCycle. Both are broadcast in SIB1.
● modificationPeriodCoeff is the coefficient of the modification period,
indicating the minimum number of times the UE monitors paging messages
within the BCCH modification period. It is set to 2 and cannot be configured.
● defaultPagingCycle is the default paging cycle in units of radio frames. It is
specified by the NRDUCellPagingConfig.DefaultPagingCycle parameter.
The BCCH modification period starts when its start frame SFN meets the SFN mod
m = 0 requirement.

4.1.1.3 System Information Acquisition


A UE obtains system information in the following order:
1. MIB: The BCH transport format is predefined. Therefore, the UE receives the
MIB without obtaining any other information from the network.
2. SIB1: After receiving the MIB, the UE receives SIB1 according to the
configuration specified by the MIB.
3. OSI: After receiving SIB1, the UE receives OSI according to the configuration
specified by SIB1.
– If SIB1 indicates that the OSI is delivered in broadcast mode, the UE
receives this OSI in the corresponding SI window.
– If SIB1 indicates that the OSI is delivered in on-demand delivery mode,
the UE receives this OSI in a way depending on whether SI-RequestConfig
is configured in SIB1.

▪ If SI-RequestConfig is configured, the UE requests the OSI through


Msg1. In this mode, the gNodeB does not allocate dedicated physical
random access channel (PRACH) resources for the OSI. This mode
applies when PRACH resources are insufficient.

▪ If SI-RequestConfig is not configured, the UE requests the OSI


through Msg3. In this mode, the gNodeB allocates dedicated PRACH
resources for the OSI. This mode applies when PRACH resources are
sufficient.
NOTE

To prevent a UE from repeatedly sending requests, if SI-RequestConfig is


configured, the gNodeB acknowledges the reception of a request through Msg4
and immediately broadcasts the requested OSI. If SI-RequestConfig is not
configured, the gNodeB acknowledges the reception of a request through Msg2
and immediately broadcasts the requested OSI.

When a UE enters a new serving cell, the UE obtains cell system information in
the following scenarios:
● The UE selects the cell after being powered on.
● The UE is to reselect to the new serving cell.
● The UE completes a handover process.
● The UE is transferred to the NG-RAN from another RAT.
● The UE returns from a non-coverage area to a coverage area.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 16


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

To save power, the UE does not repeatedly obtain system information during each
system information broadcast period. Instead, the UE re-obtains serving cell
system information only when the serving cell broadcast parameters change or
the system information validity period expires. The UE re-obtains the cell system
information in the following scenarios:
● The UE receives a system information change notification in a Short Message
from the gNodeB.
The UE reads the valueTag value of system information in SIB1 and compares
it with the one acquired last time. If the value has changed, the UE learns
that the system information has changed, and then re-obtains the system
information. If the value has not changed, the UE learns that the system
information has not changed, and will not re-obtain the system information.
● The system information validity period expires.
The system information stored on the UE is only valid for 3 hours. After 3
hours, the UE reads all of the system information regardless of whether the
valueTag value changes.
When the system information changes, the UE performs the following operations,
as shown in Figure 4-4.

Figure 4-4 System information update procedure

1. The UE receives the Short Message in the current BCCH modification period
(n).
2. The UE receives updated system information in the next BCCH modification
period (n+1).
In the figure, gray and blue blocks indicate the same system information type. A
color change indicates content change. The white system information blocks
remain unchanged during the procedure.

4.1.2 Paging

4.1.2.1 Triggering of Paging


The network searches for UEs by paging. There are two paging types, which differ
in triggering sources.
● 5GC paging: triggered by the 5GC. When downlink data needs to be sent to a
UE in the RRC_IDLE state, the 5GC triggers paging for the UE.
● RAN paging: triggered by the gNodeB. When downlink data needs to be sent
to a UE in the RRC_INACTIVE state, the gNodeB triggers paging for the UE.
Figure 4-5 shows the message transmission for a paging procedure triggered by
the 5GC.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 17


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Figure 4-5 Paging message transmission

4.1.2.2 Paging Mechanism over the Air Interface


Figure 4-6 shows the transmission path of paging messages. The path is as
follows: PCCH (paging control channel, a logical channel) -> PCH (paging channel,
a transport channel) -> PDSCH (a physical channel).

Figure 4-6 Paging message transmission path

The gNodeB can schedule UEs based on the first in first out (FIFO) policy and
priority-based policy. The NRDUCellPagingConfig.PagingTransPolicy parameter

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 18


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

specifies the policy for the gNodeB to transmit paging messages over the air
interface.

● FIFO policy
When the NRDUCellPagingConfig.PagingTransPolicy parameter is set to
FIFO, the paging messages that reach the gNodeB earlier on a paging
occasion are preferentially combined into one paging message. (A maximum
of 32 paging messages can be combined.) The gNodeB then delivers the
combined paging message to UEs on this paging occasion.
If the FIFO policy is used when there are a large number of paging messages,
the paging messages with higher priorities may not be promptly transmitted,
and the delay of the paging messages with higher priorities may increase.
● Priority-based policy
When the NRDUCellPagingConfig.PagingTransPolicy parameter is set to
PRI_DIFFERENTIATED, the paging messages with higher priorities on a
paging occasion are preferentially combined into one paging message. (A
maximum of 32 paging messages can be combined.) The gNodeB then
delivers the combined paging message to UEs on this paging occasion.
If the priority-based policy is used when there are a large number of paging
messages, the paging messages with lower priorities may be discarded, and
the waiting time before transmitting the paging messages with higher
priorities over the air interface decreases, shortening response time for the
paging messages with higher priorities.

As described in section 7.1 "Discontinuous Reception for paging" in 3GPP TS


38.304 V15.4.0, UEs in the RRC_IDLE or RRC_INACTIVE state can use discontinuous
reception (DRX) to reduce power consumption. A UE receives a paging message
over the air interface only at a fixed time-domain position, as shown in Figure
4-7.

Figure 4-7 Paging mechanism

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 19


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

● T: indicates the paging cycle.


● PF: indicates the paging frame, which consists of multiple POs.
● PO: indicates the paging occasion. It is a set of PDCCH monitoring
opportunities and consists of multiple slots. One PO includes S SSB
(synchronization signal and PBCH block) beams (S is determined by ssb-
PositionsInBurst in SIB1). As stipulated in section 6.2.2 "Message definitions"
of 3GPP TS 38.331 V15.5.0, a maximum of 32 UEs can be paged within a PO.
● SSB: The paging messages sent on each SSB beam are the same.
The formulas for PF and PO are as follows:
● (SFN + PF_offset) mod T = (T div N) x (UE_ID mod N)
All SFN values that meet the preceding formula indicate PFs.
● i_s of a PO = floor (UE_ID/N) mod Ns
After a PF is calculated, the time when a UE receives the paging message can
be obtained by calculating the position i_s of the corresponding PO of the UE
in the PF. The i_s indicates the start position of a set of PDCCH monitoring
opportunities. The UE starts to receive paging messages in the i_sth PO.
Huawei uses the following values of the preceding elements:
● T: indicates the paging cycle and is equal to min(Default paging cycle, UE-
specific DRX cycle), where:
– The default paging cycle is specified by the
NRDUCellPagingConfig.DefaultPagingCycle parameter.
– The UE-specific DRX cycle is carried in the Paging DRX IE of the paging
message from the AMF to the gNodeB.
● PF_offset: indicates the frame offset of the PF, and is fixed to 1.
● N: indicates the number of PFs contained in a paging cycle T, and is fixed to
T/2.
● UE_ID: indicates the UE identity delivered by the core network. The UE
identity equals the value of 5G-S-TMSI mod 1024.
● Ns: indicates the number of POs contained in a PF, and is fixed to 1.

4.1.3 Random Access


After the cell search is complete, a UE achieves downlink synchronization with the
cell and can receive downlink data. However, the UE has not achieved uplink
synchronization with the cell yet. The UE establishes a connection with the cell
and achieves uplink synchronization through RA to perform uplink transmission.
The UE initiates RA using specific PRACH time-frequency resources. When the UE
initiates RA, an RA preamble is transmitted. The RA preamble is used to inform the
gNodeB of an RA request, allowing the gNodeB to estimate the transmission delay
between the gNodeB and the UE. For details about RA preambles, see Channel
Management.
RA has the following mechanisms:
● Contention-based RA
Preambles are randomly selected by UEs and such preambles are random. In
this case, conflicts may exist among the preambles selected by different UEs.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 20


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

The gNodeB uses a contention resolution mechanism to handle access


requests. The RA result is random and not all RA procedures succeed.
● Non-contention-based RA
Preambles are allocated by the gNodeB to UEs and such preambles are
dedicated. Therefore, there is no preamble conflict. When dedicated
preambles are insufficient, the gNodeB instructs UEs to initiate contention-
based RA.

The RA mechanism selected varies with the triggering scenario. For details about
RA triggering scenarios and mechanisms, see 4.1.3.1 RA Triggering Scenarios and
RA Mechanisms.

The RA procedure varies with the mechanism. For details about RA procedures, see
4.1.3.2 RA Procedures.

4.1.3.1 RA Triggering Scenarios and RA Mechanisms


Table 4-2 describes RA triggering scenarios and RA mechanisms.

Table 4-2 RA triggering scenarios and RA mechanisms

Triggering Scenario Description Mechanism


Scenario

Initial RRC When a UE needs to transit Contention-based RA


connection setup from RRC_IDLE to
RRC_CONNECTED, the UE
initiates RA to establish an RRC
connection. If the state
transition is triggered by the UE,
the UE initiates RA. If the state
transition is required by the
gNodeB, the gNodeB instructs
the UE to initiate RA through a
paging procedure.

RRC connection After detecting a radio link Contention-based RA


reestablishment failure, a UE initiates RA to
reestablish an RRC connection.

Handover During a handover, a UE Non-contention-based


initiates RA in the target cell. RA is the first choice.
Contention-based RA is
used when dedicated
preambles of the
gNodeB are used up.

Downlink data When a gNodeB needs to send Non-contention-based


arrival downlink data to an RA is preferentially used
RRC_CONNECTED UE in an if the UE reports the SSB
uplink out-of-synchronization index. In other scenarios,
state, the gNodeB instructs the contention-based RA is
UE to initiate RA. used.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 21


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Triggering Scenario Description Mechanism


Scenario

Uplink data When an RRC_CONNECTED UE Contention-based RA


transmission in an uplink out-of-
synchronization state needs to
send uplink data to a gNodeB,
the UE initiates RA.

Transition from When a UE needs to transit Contention-based RA is


RRC_INACTIVE to from RRC_INACTIVE to used when the UE
RRC_CONNECTED RRC_CONNECTED, the UE proactively transits from
initiates RA. If the state RRC_INACTIVE to
transition is triggered by the UE, RRC_CONNECTED. Non-
the UE initiates RA. If the state contention-based RA is
transition is required by the used when the gNodeB
gNodeB, the gNodeB instructs initiates paging to
the UE to initiate RA through a instruct the UE to transit
paging procedure. from RRC_INACTIVE to
RRC_CONNECTED.

RA-based OSI When a type of OSI is delivered Non-contention-based


request in on-demand delivery mode, a RA
UE requests this type of OSI
through Msg1.

4.1.3.2 RA Procedures
The contention-based RA procedure slightly differs from the non-contention-based
RA procedure. For details about RA procedures, see section 5.1 "Random Access
procedure" in 3GPP TS 38.321 V15.5.0.

4.1.3.2.1 Contention-based RA Procedure


Figure 4-8 shows how contention-based RA works.

Figure 4-8 Contention-based RA procedure

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 22


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

The contention-based RA procedure is as follows:

1. A UE sends an RA preamble.
The UE sends an RA preamble using Msg1. Figure 4-8 shows the RA preamble
transmission procedure.

Figure 4-9 RA preamble transmission procedure

a. The UE obtains the PRACH configuration from SIB1.


The UE obtains the time-frequency domain position for transmitting an
RA preamble based on the PRACH configuration.
b. The UE randomly selects an RA preamble with an even possibility.
Each SSB corresponds to a unique preamble index. Therefore, before
selecting an RA preamble, the UE first selects an SSB, and then
determines the RA preamble based on the SSB. The UE compares the
RSRP values of all SSBs in the cell with the RSRP threshold and selects an
SSB whose RSRP value is greater than the threshold. The RSRP threshold
is indicated by the rsrp-ThresholdSSB IE in 3GPP TS 38.331 V15.5.0 and
specified by the NRDUCellPrach.RsrpThldForSsbSelection parameter. If
no SSB meets the requirement, the UE selects an SSB randomly. For
details, see section 5.1.2 "Random Access Resource selection" in 3GPP TS
38.321 V15.5.0.
c. The UE sends the RA preamble.
2. The gNodeB sends an RA response.
After receiving the RA preamble from the UE, the gNodeB obtains the timing
alignment information. The gNodeB sends an RA response to the UE over the
PDSCH through Msg2. One PDSCH can carry RA responses to multiple UEs at
the same time. The specific information carried in the RA response includes:
RA-preamble identifier, timing alignment information, UL grant, and
temporary C-RNTI.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 23


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

After the UE sends the RA preamble, it monitors the PDCCH within the RA
response window until an RA response is received over the PDSCH.
– If the UE receives a response containing an RA-preamble identifier which
is the same as the identifier contained in the transmitted RA preamble,
the response is successful. The UE proceeds with 3.
– If the UE does not receive a response within the RA response window or
the verification of the response fails, the response fails. In this case, if the
number of RA attempts is smaller than the upper limit (specified by the
NRDUCellPrach.MaxPreambleTransCnt parameter), the UE makes
another RA attempt. Otherwise, the RA procedure fails.
3. The UE performs uplink scheduled transmission.
The UE determines the timing for scheduled transmission based on timing
alignment information, and sends it to the gNodeB through Msg3.
4. The gNodeB assists the UE in contention resolution.
After the UE sends Msg3, a contention resolution timer of 64 ms starts. The
gNodeB assists the UE in contention resolution by sending the C-RNTI on the
PDCCH or the UE Contention Resolution Identity IE on the PDSCH.
– The UE keeps monitoring the PDCCH before the timer expires. The UE
considers the contention resolution successful (that is, successful access
of the UE) and stops the timer if either of the following conditions is met.
Otherwise, the UE does not stop the timer.

▪ The UE obtains the C-RNTI over the PDCCH through Msg4. In this
case, the UE stops the contention resolution timer and discards the
temporary C-RNTI.

▪ The UE obtains the temporary C-RNTI over the PDCCH through


Msg4. The MAC packet data unit (PDU) is successfully decoded.
Specifically, the Contention Resolution Identity IE in the MAC PDU
received by the UE is the same as that carried in Msg3 sent by the
UE. In this case, the UE stops the contention resolution timer and
sets the temporary C-RNTI to the C-RNTI.
– If the contention resolution timer expires, the UE discards the temporary
C-RNTI and considers the contention resolution failed.
Then, the UE makes another RA attempt if the number of RA attempts
has not reached the upper limit (specified by the
NRDUCellPrach.MaxPreambleTransCnt parameter). Otherwise, the RA
procedure fails.

4.1.3.2.2 Non-Contention-based RA Procedure


Figure 4-10 shows how non-contention-based RA works. Unlike contention-based
RA, non-contention-based RA does not involve contention resolution because RA
preambles are allocated by the gNodeB. Other procedures are the same between
non-contention-based RA and contention-based RA.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 24


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Figure 4-10 Non-contention-based RA procedure

The non-contention-based RA procedure is as follows:


1. The gNodeB allocates an RA preamble to a UE.
In handover scenarios, the MobilityControlInfo IE sent by the source gNodeB
carries the RA preamble allocated to the UE. When allocating an RA preamble
to a UE, the gNodeB also indicates an SSB to the UE, through PDCCH or RRC
signaling.
2. The UE sends the RA preamble.
Figure 4-11 shows how the RA preamble is transmitted.

Figure 4-11 RA preamble transmission procedure

a. The UE obtains the PRACH configuration from SIB1.


The UE obtains the time-frequency domain position for transmitting the
RA preamble based on the PRACH configuration.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 25


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

NOTE

After obtaining the PRACH configuration, the UE selects the SSB as indicated by
the gNodeB. For details, see section 5.1.2 "Random Access Resource selection" in
3GPP TS 38.321 V15.5.0.
● When selecting an SSB according to the PDCCH indication, the UE directly
selects the indicated SSB, and continues with the follow-up steps of the non-
contention-based RA procedure.
● When selecting an SSB according to the RRC signaling indication, the UE
needs to compare the RSRP value of the indicated SSB with the RSRP
threshold (corresponding to the rsrp-ThresholdSSB IE in 3GPP TS 38.331
V15.5.0 and specified by the NRDUCellPrach.RsrpThldForSsbSelection
parameter). If the RSRP value exceeds the threshold, the UE selects the
indicated SSB and continues with the follow-up steps of the non-contention-
based RA procedure. Otherwise, the UE initiates contention-based RA.
b. The UE sends the RA preamble.
3. The gNodeB sends an RA response.
In handover scenarios, the RA response carries timing alignment information
and UL grant.
After the UE sends the RA preamble, it monitors the PDCCH within the RA
response window until an RA response is received.
– If the UE receives a response within the RA response window, the UE
considers the RA response successful. The UE proceeds with 4.
– If the UE does not receive a response within the RA response window, the
UE considers the RA response failed. In this case, if the number of RA
attempts is smaller than the upper limit (specified by the
NRDUCellPrach.MaxPreambleTransCnt parameter), the UE makes
another RA attempt. Otherwise, the RA procedure fails.
4. The UE performs uplink scheduled transmission.
The UE determines the timing for scheduled transmission based on timing
alignment information, and sends it to the gNodeB through Msg3.

4.1.4 RRC Connection Management


RRC connection management involves the following:

● RRC connection setup: RRC connection setup is a procedure for establishing


the SRB1. After the SRB1 is established, a UE enters connected mode. For
details about RRC connection setup, see 4.1.4.1 RRC Connection Setup.
● RRC connection reconfiguration: RRC connection reconfiguration is a
procedure for modifying RRC connections with established SRB1s. For details
about RRC connection reconfiguration, see 4.1.4.2 RRC Connection
Reconfiguration.
● RRC connection release: RRC connection release is a procedure for releasing
the RRC connection between a UE and a gNodeB, including releasing all radio
bearer resources. For details about RRC connection release, see 4.1.4.3 RRC
Connection Release.
● RRC connection reestablishment: RRC connection reestablishment is a service
processing procedure initiated by a UE for quick RRC connection setup. The UE
can initiate an RRC connection reestablishment procedure only when an RRC
connection has been successfully set up and the security mode has been

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 26


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

successfully enabled. For details about RRC connection reestablishment, see


4.1.4.4 RRC Connection Reestablishment.
● Uplink out-of-synchronization management: Uplink out-of-synchronization
management enables a gNodeB to maintain uplink timing for a UE in
connected mode in real time so that the UE remains in the uplink
synchronization state. For details about uplink out-of-synchronization
management, see 4.1.4.5 Uplink Out-of-Synchronization Management.
● UE inactivity management: UE inactivity management enables a gNodeB to
detect an inactive UE in connected mode and perform inactivity management
on the UE. This prevents the inactive UE from occupying system resources for
a long period. For details about UE inactivity management, see 4.1.4.6 UE
Inactivity Management.

4.1.4.1 RRC Connection Setup


Figure 4-12 shows the RRC connection setup procedure.

Figure 4-12 RRC connection setup procedure

1. A UE sends Msg1 to the gNodeB to initiate contention-based RA.


2. The gNodeB sends an RA response to the UE through Msg2.
3. The UE sends an RRCSetupRequest message carrying the RRC connection
setup cause and UE identity to the gNodeB, requesting the setup of an RRC
connection. During the initial RA, the RRCSetupRequest message is sent
through Msg3. In the preceding information:
– The RRC connection setup cause is specified by the upper layer.
– The UE identity can be the 5G-S-TMSI or a random number.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 27


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

▪ If the upper layer provides the 5G-S-TMSI, the message contains the
5G-S-TMSI.

▪ If no 5G-S-TMSI information is provided, a random number between


0 and (239 – 1) is generated and sent to the gNodeB.
4. The gNodeB sets up UE context.
If the gNodeB receives multiple RRCSetupRequest messages from the UE
within the time window specified by the
gNBConnStateTimer.UuMessageWaitingTimer parameter, the gNodeB
handles only the most recent one.
5. The gNodeB performs the SRB1 admission and resource allocation.
If the SRB1 admission or resource allocation fails, the gNodeB responds to the
UE with an RRCReject message. The RRC connection setup fails. Otherwise, 6
and 7 are performed.
6. The gNodeB sends an RRCSetup message containing SRB1 resource
configurations to the UE.
7. The UE configures radio resources based on the SRB1 resource information
indicated by the RRCSetup message. It then sends the gNodeB an
RRCSetupComplete message indicating that the RRC connection setup is
complete.
After the gNodeB sends the RRCSetup message, it starts a timer to wait for
the RRCSetupComplete message. The timer is specified by the
gNBConnStateTimer.UuMessageWaitingTimer parameter. If the gNodeB
does not receive the RRCSetupComplete message from the UE before the
timer expires, the RRC connection setup fails.

4.1.4.2 RRC Connection Reconfiguration


Figure 4-13 shows the RRC connection reconfiguration procedure.

Figure 4-13 RRC connection reconfiguration procedure

1. The gNodeB sends an RRCReconfiguration message to a UE to initiate an RRC


connection reconfiguration procedure. The RRC connection reconfiguration
procedure includes the following:
– SRB2 setup
After encryption and integrity protection are complete during UE context
setup, the gNodeB sends an RRCReconfiguration message containing the
srb-ToAddModList IE to the UE, instructing the UE to set up SRB2. For
details, see 4.1.5.1 Context Setup.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 28


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

– SRB1/SRB2 modification
The gNodeB sends an RRCReconfiguration message containing the srb-
ToAddModList IE to the UE, instructing the UE to modify SRB1 or SRB2.
The UE reconfigures the Packet Data Convergence Protocol (PDCP) entity,
Radio Link Control (RLC) entity, and dedicated control channel (DCCH) as
instructed. SRB1/SRB2 modification can be triggered in many scenarios,
such as context modification.
– DRB setup
During PDU session setup, the AMF sends a PDU SESSION RESOURCE
SETUP REQUEST message to the gNodeB to trigger DRB setup. The
gNodeB sends an RRCReconfiguration message containing the drb-
ToAddModList IE to the UE, instructing the UE to set up a DRB. For
details, see 4.1.6.1 PDU Session Setup.
– DRB modification
During PDU session modification, the AMF sends a PDU SESSION
RESOURCE MODIFY REQUEST message to the gNodeB to trigger DRB
modification. The gNodeB sends an RRCReconfiguration message
containing the drb-ToAddModList IE to the UE, instructing the UE to
modify a DRB. For details, see 4.1.6.2 PDU Session Modification.
– DRB release
During PDU session release, the AMF sends a PDU SESSION RESOURCE
RELEASE COMMAND message to the gNodeB to trigger DRB release. The
gNodeB sends an RRCReconfiguration message containing the drb-
ToReleaseList IE to the UE, instructing the UE to release a DRB. For
details, see 4.1.6.3 PDU Session Release.
2. The UE reconfigures radio bearers based on the instructions in the
RRCReconfiguration message, and then sends the gNodeB an
RRCReconfigurationComplete message indicating that the RRC connection
reconfiguration is complete.

4.1.4.3 RRC Connection Release


After an RRC connection is released, the signaling connection between the UE and
gNodeB and all the involved radio bearers (SRB1, SRB2, and DRB) are released.

RRC connection release is triggered by context release. For details about RRC
connection release, see 4.1.5.3 Context Release.

4.1.4.4 RRC Connection Reestablishment


RRC connection reestablishment is a service processing procedure initiated by a UE
for quick RRC connection reestablishment. The UE can initiate this procedure only
when an RRC connection has been set up and the security mode has been
enabled. The procedure is triggered in any of the following scenarios:

● A radio link failure (RLF) occurs.


The UE detects an RLF when any of the following conditions is met. For
details, see section 7.1.1 "Timers (Informative)" in 3GPP TS 38.331 V15.5.0.
– The timer specified by the NRDUCellUeTimerConst.T310 parameter
expires.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 29


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

– RA fails and the timer specified by the NRDUCellUeTimerConst.T311


parameter is not running.
– The number of RLC retransmissions reaches the maximum.
● An inter-RAT outgoing handover fails.
● An intra-RAT handover fails.
● Integrity check fails.
● RRC connection reconfiguration fails.

Figure 4-14 shows the RRC connection reestablishment procedure.

Figure 4-14 RRC connection reestablishment procedure

1. The UE sends Msg1 to the gNodeB to initiate contention-based RA.


2. The gNodeB sends an RA response to the UE through Msg2.
3. The UE reestablishes SRB1 and sends the gNodeB an
RRCReestablishmentRequest message carrying the c-RNTI, physCellId, and
shortMAC-I used before reestablishment.
4. After receiving the RRCReestablishmentRequest message, the gNodeB
performs the following:

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 30


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

a. Based on the c-RNTI, physCellId, and shortMAC-I, the gNodeB searches


for the UE context before RRC connection reestablishment.
b. The gNodeB restores RRC configuration information and security
information according to the UE context.
c. The gNodeB reestablishes SRB1.
d. By using SRB1, the gNodeB sends an RRCReestablishment message
carrying the nextHopChainingCount IE to the UE, instructing the UE to
update the AS security key.

NOTE

If the gNodeB cannot find the UE context (for example, in inter-gNodeB RRC
connection reestablishment scenarios), it directly sets up an RRC connection after
receiving an RRC connection reestablishment request from the UE. For details on RRC
connection setup, see 4.1.4.1 RRC Connection Setup.
5. The UE responds the gNodeB with an RRCReestablishmentComplete message.
6. The gNodeB continues to reestablish SRB2 and DRB.
7. The gNodeB sends an RRCReconfiguration message to the UE, instructing the
UE to reestablish SRB2 and DRB.
8. The UE sends an RRCReconfigurationComplete message to the gNodeB. The
RRC connection reestablishment procedure is complete.

4.1.4.5 Uplink Out-of-Synchronization Management


After the RA is successful, a UE sends a sounding reference signal (SRS) or
demodulation reference signal (DMRS) to the gNodeB and the gNodeB performs
measurements.
● If the gNodeB can obtain timing alignment information, the gNodeB sends a
Timing Advance Command to the UE. The gNodeB and UE use the same
uplink time alignment timer (specified by the
NRDUCellUlTaConfig.UlTimeAlignmentTimer parameter).
– Before the uplink time alignment timer expires, both the gNodeB and the
UE determine that uplink synchronization is achieved. Once a Timing
Advance Command is received, the UE restarts the uplink time alignment
timer. The gNodeB restarts the uplink time alignment timer upon
receiving an ACK to the Timing Advance Command from the UE.
– A UE cannot achieve uplink synchronization and enters the out-of-
synchronization state when the uplink time alignment timer expires in
any of the following cases:

▪ The UE does not receive a Timing Advance Command before the


uplink time alignment timer expires. In this case, the uplink time
alignment timer on the UE will expire.

▪ The gNodeB does not receive an ACK to the Timing Advance


Command from the UE before the uplink time alignment timer
expires. In this case, the uplink time alignment timer on the gNodeB
will expire.
In out-of-synchronization state, if the gNodeB or the UE needs to send
data, the UE must initiate an RA procedure and restart the uplink time
alignment timer.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 31


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

When the parameter value of the uplink time alignment timer is set to
INFINITY, the uplink time alignment timer will never expire.
● If the gNodeB cannot obtain timing alignment information, uplink
synchronization cannot be maintained for the UE and out-of-synchronization
occurs.
When the UE is in the uplink out-of-synchronization state, the gNodeB instructs
the UE to initiate an RA procedure for downlink data transmission or the UE
initiates an RA procedure to restore uplink synchronization for uplink data
transmission.

4.1.4.6 UE Inactivity Management


After detecting an inactive UE, the gNodeB performs inactivity management on
the UE. This prevents the inactive UE from occupying system resources for a long
period. A UE becomes inactive when it does not transmit or receive data or when
it disconnects from the gNodeB.
When detecting that a UE is in any of the following situations, the gNodeB
considers the UE inactive:
● The gNodeB detects that the UE is in the signaling-only connection (no DRB)
for more than 60 seconds.
● After the UE sets up a DRB, the gNodeB detects that the UE does not transmit
or receive any data (excluding MAC CEs) within the length of the UE inactivity
timer (specified by the NRDUCellQciBearer.UeInactivityTimer parameter).
The UE may set up multiple DRBs, and each DRB corresponds to a QCI. If
different UE inactivity timer lengths are configured for these QCIs by setting
the NRDUCellQciBearer.UeInactivityTimer parameter, the maximum value
takes effect.
After considering the UE inactive, the gNodeB initiates a UE state transition or an
RRC connection release procedure.
● If the RRC_INACTIVE_SWITCH option of the
NRCellAlgoSwitch.InactiveStrategySwitch parameter is selected, the
gNodeB instructs the UE to switch from the RRC_CONNECTED state to
RRC_INACTIVE state.
● If the RRC_INACTIVE_SWITCH option of the
NRCellAlgoSwitch.InactiveStrategySwitch parameter is deselected, the
gNodeB sends a UE CONTEXT RELEASE REQUEST message carrying the
release cause "User Inactivity" to the AMF. The gNodeB initiates an RRC
connection release procedure.

4.1.5 Context Management


Context management includes context setup, context modification, and context
release. For details, see 4.1.5.1 Context Setup, 4.1.5.2 Context Modification, and
4.1.5.3 Context Release. For more details about context management, see section
8.3 "UE Context Management Procedures" in 3GPP TS 38.413 V15.5.0.

4.1.5.1 Context Setup


After the RRC connection is set up, the gNodeB sends an INITIAL UE MESSAGE to
trigger NG-C connection setup and initial context setup procedures. The message

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 32


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

contains the PDU session, security key, handover restriction list, UE radio
capability, and security capability.
Figure 4-15 shows the initial context setup procedure.

Figure 4-15 Context setup procedure

1. After the RRC connection is set up, the UE sends an RRCSetupComplete


message to the gNodeB. The RRCSetupComplete message contains the
selectedPLMN-Identity, registeredAMF, s-nssai-list, and NAS message.
2. The gNodeB allocates a dedicated RAN-UE-NGAP-ID to the UE, and selects an
AMF node based on the selectedPLMN-Identity, registeredAMF, and s-nssai-
list. Then, it sends the NAS message carried in the RRCSetupComplete
message to the AMF through an INITIAL UE MESSAGE, triggering an NG-C
connection setup procedure.
3. The gNodeB transparently transmits the NAS direct transfer messages
between the UE and AMF to complete the identity query, authentication, NAS
security mode, and registration.
4. The AMF sends an INITIAL CONTEXT SETUP REQUEST message to the
gNodeB, triggering an initial context setup procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 33


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

NOTE

● Only when the INITIAL CONTEXT SETUP REQUEST message does not carry the UE
Radio Capability IE, the gNodeB sends a UECapabilityEnquiry message to the UE
after security mode procedure completion to initiate a UE capability query
procedure, as indicated by 7 to 9. Otherwise, 7 to 9 are skipped.
● Only when the INITIAL CONTEXT SETUP REQUEST message carries the PDU
Session Resource Setup Request List IE, the gNodeB sends an RRCReconfiguration
message with encryption and integrity protection implemented to the UE after UE
capability query completion, instructing the UE to set up SRB2 and a DRB, as
indicated by 10 and 11. Otherwise, 10 and 11 are skipped.
5. The gNodeB sends a SecurityModeCommand message to the UE, instructing
the UE to start integrity protection and encryption. Then, downlink encryption
starts.
6. Based on the integrity protection and encryption algorithms indicated by the
SecurityModeCommand message, the UE derives a key and sends a
SecurityModeComplete message to the gNodeB. Then, uplink encryption
starts.
7. The gNodeB sends a UECapabilityEnquiry message to the UE to initiate a UE
capability query procedure.
8. The UE sends a UECapabilityInformation message carrying the UE capability
information to the gNodeB.
9. The gNodeB transparently transmits the UE capability to the AMF through a
UE RADIO CAPABILITY INFO INDICATION message.
10. The gNodeB sends an RRCReconfiguration message to the UE, instructing the
UE to set up SRB2 and a DRB.
After encryption and integrity protection are complete during dedicated NG-C
connection setup, the gNodeB sends an RRCReconfiguration message
containing the srb-ToAddModList IE to the UE, instructing the UE to set up
SRB2 and a DRB.
11. After receiving the RRCReconfiguration message, the UE starts the setup of
SRB2 and a DRB. The UE performs the following operations as instructed:
– Sets up a PDCP entity and configures related security parameters.
– Sets up and configures an RLC entity.
– Sets up and configures a DCCH.
After SRB2 and a DRB are set up, the UE sends an
RRCReconfigurationComplete message to the gNodeB.
12. The gNodeB sends an INITIAL CONTEXT SETUP RESPONSE message to the
AMF.

4.1.5.2 Context Modification


Figure 4-16 shows the context modification procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 34


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Figure 4-16 Context modification procedure

1. The AMF sends a UE CONTEXT MODIFICATION REQUEST to the gNodeB,


triggering a UE context modification procedure.
NOTE

When the UE CONTEXT MODIFICATION REQUEST message contains the Security Key
IE, the gNodeB triggers a key update procedure. During the key update procedure, the
gNodeB initiates an RRC connection reconfiguration procedure and the UE
reconfigures radio bearers, as indicated by 2 and 3. Otherwise, 2 and 3 are skipped.
2. After deriving a key based on the Security Key IE, the gNodeB sends an
RRCReconfiguration message to the UE, instructing the UE to update the key.
For details about key derivation, see 3GPP TS 33.501 V15.5.0.
3. After updating the key, the UE sends an RRCReconfigurationComplete
message to the gNodeB.
4. The gNodeB sends the AMF a UE CONTEXT MODIFICATION RESPONSE
message indicating that the UE context modification is complete.

4.1.5.3 Context Release


Context release involves releasing the signaling connection between the gNodeB
and 5GC. A context release procedure can be initiated by the gNodeB or the AMF.
● gNodeB-triggered context release: The gNodeB sends a UE CONTEXT RELEASE
REQUEST message to the AMF upon detecting a UE connection exception,
such as the UE inactivity.
● AMF-triggered context release: The AMF sends a UE CONTEXT RELEASE
COMMAND message to the gNodeB when the AMF decides to abort the
service of a UE or a UE decides to abort the service and informs the AMF
through NAS signaling.

In scenarios with only the context of a UE but no PDU sessions, the UE may
automatically release the context after a period. However, the network does not
detect the release. When such an exception occurs, the gNodeB resources are
occupied for an extended duration. To avoid this issue, a protection measure is
introduced. In this case, the gNodeB monitors whether NAS signaling is exchanged
between the UE and the AMF within the length of a timer, and if not, triggers a

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 35


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

context release. The timer is specified by the


gNBConnStateTimer.SigUeNoNasMsgTransTmr parameter.
Figure 4-17 shows the context release procedure.

Figure 4-17 Context release procedure

1. The gNodeB sends a UE CONTEXT RELEASE REQUEST message to the AMF,


requesting a context release.
NOTE

1 is involved only when the context release is triggered by the gNodeB.


2. The AMF sends a UE CONTEXT RELEASE COMMAND message to the gNodeB,
instructing the gNodeB to release the UE context.
3. The gNodeB sends an RRCRelease message to the UE, instructing the UE to
release the RRC connection.
4. The gNodeB sends the AMF a UE CONTEXT RELEASE COMPLETE message
indicating that the context release is complete.
After receiving the UE CONTEXT RELEASE COMPLETE message, the AMF
releases the NAS context information and AS context information
corresponding to the UE. Then, the UE switches from the connected mode to
the idle mode.

4.1.6 PDU Session Management


PDU session management involves the following:
● PDU session setup: a procedure for setting up DRBs and NG-U transmission
tunnels for QoS flows corresponding to one or more PDU sessions. For details,
see 4.1.6.1 PDU Session Setup.
● PDU session modification: a procedure for modifying DRBs and NG-U
transmission tunnels for QoS flows corresponding to one or more PDU
sessions. For details, see 4.1.6.2 PDU Session Modification.
● PDU session release: a procedure for releasing DRBs and NG-U transmission
tunnels for QoS flows corresponding to one or more PDU sessions. For details,
see 4.1.6.3 PDU Session Release.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 36


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

4.1.6.1 PDU Session Setup


Figure 4-18 shows the PDU session setup procedure.

Figure 4-18 PDU session setup procedure

1. The AMF sends a PDU SESSION RESOURCE SETUP REQUEST message to the
gNodeB. The message contains a list of PDU sessions to be set up, a list of
QoS flows of each PDU session, and the quality attribute of each QoS flow.
2. The gNodeB maps QoS flows to DRBs based on the QoS flow quality
attributes and MML-configured policy. It then sends an RRCReconfiguration
message to the UE, instructing the UE to set up DRBs.
3. Based on the drb-ToAddModList IE contained in the RRCReconfiguration
message, the UE sets up DRBs. The UE performs the following operations as
instructed:
– Sets up a PDCP entity and configures related security parameters.
– Sets up and configures an RLC entity.
– Sets up and configures a dedicated traffic channel (DTCH).
After setting up DRBs, the UE sends an RRCReconfigurationComplete message
to the gNodeB.
4. The gNodeB sends the AMF a PDU SESSION RESOURCE SETUP RESPONSE
message indicating that the PDU session setup is complete.

4.1.6.2 PDU Session Modification


Figure 4-19 shows the PDU session modification procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 37


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Figure 4-19 PDU session modification procedure

1. The AMF sends a PDU SESSION RESOURCE MODIFY REQUEST message to the
gNodeB. The message contains information including a QoS Flow Add or
Modify Response List and a QoS Flow to Release List.
2. The gNodeB modifies DRBs based on the QoS policy and sends the UE an
RRCReconfiguration message carrying the drb-ToAddModList IE. DRB
modification is performed in the following three scenarios:
– Adding a DRB: New QoS flows cannot be mapped to the existing DRBs.
And a new DRB needs to be added to meet the QoS requirements.
– Deleting a DRB: If all QoS flows mapped to a DRB have been deleted, this
DRB needs to be deleted.
– Modifying a DRB: A QoS flow mapping needs to be added to or deleted
from an existing DRB.
3. The UE reconfigures the PDCP entity, RLC entity, and DTCH according to the
instructions in the RRCReconfiguration message. After reconfiguration, the UE
sends an RRCReconfigurationComplete message to the gNodeB.
4. The gNodeB sends the AMF a PDU SESSION RESOURCE MODIFY RESPONSE
message indicating that the PDU session modification is complete.

4.1.6.3 PDU Session Release


The gNodeB or the AMF can initiate a PDU session release procedure.

● gNodeB-triggered PDU session release:


– The gNodeB reallocates a new NG-U address upon detecting an NG-U
transmission fault. If the allocation fails, the gNodeB sends a PDU
SESSION RESOURCE NOTIFY message to the AMF, requesting the AMF to
initiate a PDU session release procedure.
– If the QoS flow guaranteed bit rate (GBR) cannot be provided, the
gNodeB sends a PDU SESSION RESOURCE NOTIFY message to the AMF,
requesting the AMF to initiate a PDU session release procedure.
● AMF-triggered PDU session release:

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 38


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

– The AMF sends a PDU SESSION RESOURCE RELEASE COMMAND


message to the gNodeB to trigger a PDU session release procedure when
the AMF decides to abort the service of the UE.
– The AMF sends a PDU SESSION RESOURCE RELEASE COMMAND
message to the gNodeB to trigger a PDU session release procedure when
the UE decides to abort the service and informs the AMF through NAS
signaling.

Figure 4-20 shows the PDU session release procedure.

Figure 4-20 PDU session release procedure

1. The gNodeB sends a PDU SESSION RESOURCE NOTIFY message to the AMF,
requesting the AMF to trigger a PDU session release procedure.
NOTE

1 is involved only when the PDU session release is triggered by the gNodeB.
2. The AMF sends the gNodeB a PDU SESSION RESOURCE RELEASE COMMAND
message carrying a list of PDU sessions to be released.
3. The gNodeB sends an RRCReconfiguration message to the UE, instructing the
UE to release PDU sessions.
4. Based on the drb-ToReleaseList IE contained in the RRCReconfiguration
message, the UE releases all of the resources related to the DRBs as
instructed. After the PDU session release is complete, the UE sends an
RRCReconfigurationComplete message to the gNodeB.
5. The gNodeB deletes the corresponding DRBs and NG-U transmission tunnels,
and then sends a PDU SESSION RESOURCE RELEASE RESPONSE message to
the AMF.

4.2 Network Analysis

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 39


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

4.2.1 Benefits
The functions described in this chapter are basic functions in SA networking and
are enabled by default along with cell setup.

4.2.2 Impacts
Network Impacts
None

Function Impacts
RAT Function Function Reference Description
Name Switch

Low- High- NRDUCell.Hig High Speed UEs are more likely to be out of
frequency speed hSpeedFlag Mobility synchronization in high-speed
TDD Railway mobility scenarios. The longer the
Superior uplink time alignment timer, the
Experienc higher the probability that UEs are
e out of synchronization.

FDD None None None None

Low- Low HIGH_RELIABI URLLC The full-bandwidth initial BWP is


frequency latency LITY_BASIC_S recommended when uplink
TDD and high W option of interference randomization-based
reliability the scheduling is enabled for fixed
NRDUCellAlgo resources of high-reliability services.
Switch.HighRe
liabilitySwitch
parameter

4.3 Requirements

4.3.1 Licenses
None

4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 40


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

Prerequisite Functions
RAT Function Function Reference Description
Name Switch

FDD PDCCH AGG_LVL_INIT_ Channel The PDCCH aggregation level initial


Low- aggregati SELECT_OPT_S Management selection optimization function must
frequency on level W option of be enabled before the full-bandwidth
TDD initial the initial BWP configuration function
selection NRDUCellPdcc (specified by the
optimizat h.PdcchAlgoEn INIT_BWP_FULL_BW_SW option of
ion hSwitch the
parameter NRDUCellAlgoSwitch.BwpConfigPol
icySwitch parameter) and PDCCH
rate matching function (specified by
the PDCCH_RATEMATCH_SW option
of the
NRDUCellPdsch.RateMatchSwitch
parameter) are both enabled.

Mutually Exclusive Functions


None

4.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Boards
All NR-capable main control boards and baseband processing units support this
function. To learn which main control boards and baseband processing units are
NR-capable, see the related BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.

RF Modules
All NR-capable RF modules that work in low frequency bands support this
function. For details about such RF modules, see the technical specifications of the
related RF modules in 3900 & 5900 Series Base Station Product Documentation.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 41


5G RAN
5G Networking and Signaling Feature Parameter
Description 4 Basic Signaling Procedures in SA Networking

4.4 Operation and Maintenance


The basic SA networking functions described in this chapter are enabled by default
along with cell setup. For details about cell setup in SA networking, see Cell
Management.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 42


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

5 Basic Signaling Procedures in NSA


Networking

Figure 5-1 shows the basic signaling procedures in NSA networking. In NSA
networking, signaling plane data is carried on the LTE side. Therefore, the basic
access procedures are the same as those on the LTE side. In addition, the NR B1
measurement, NG-RAN radio bearer management (including the SgNB addition
procedure), and RA to the gNodeB are added.

Figure 5-1 Basic signaling procedures in NSA networking

Basic signaling procedures in NSA networking include:

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 43


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

1. System information broadcast


System information broadcast is the first step for a UE to obtain the basic
network service information. Through the system information broadcast
procedure, the UE can obtain basic AS and NAS information. For details, see
5.1.1 System Information Broadcast.
2. Paging
When the network needs to set up a connection with a UE, the network
initiates a paging procedure to locate the UE. This procedure involves only the
terminating UE but not the originating UE. For details about the paging
procedure, see 5.1.2 Paging.
3. RA to the eNodeB
RA is a necessary procedure to establish a radio link between a UE and the
network. In NSA networking, the UE sends an access request to the eNodeB
and then the eNodeB responds to the request and allocates a random access
channel (RACH). For details, see 5.1.3 RA to the eNodeB.
4. Signaling connection management
After RA to the eNodeB is complete, the eNodeB sets up a signaling
connection between the UE and MME. Signaling connections are set up
before the security mode setup and consist of RRC connections and dedicated
S1 connections. For details, see 5.1.4 Signaling Connection Management.
5. E-UTRAN radio bearer management
E-UTRAN radio bearer management refers to SRB2 and DRB management by
the eNodeB after the security mode setup. For details, see 5.1.5 E-UTRAN
Radio Bearer Management.
6. NR B1 measurement
The eNodeB delivers the measurement configuration related to event B1 to a
UE to detect the neighboring NR cell with the best signal quality. For details,
see 5.1.6 NR B1 Measurement.
7. NG-RAN radio bearer management
NG-RAN radio bearer management refers to SRB3 and DRB management by
the gNodeB. For details, see 5.1.7 NG-RAN Radio Bearer Management.
8. RA to the gNodeB
A UE sends an access request to the gNodeB. For details, see 5.1.8 RA to the
gNodeB.

5.1 Principles

5.1.1 System Information Broadcast


In NSA networking, system information broadcast includes system information
broadcast on the LTE side and that on the NR side.
● For details about the procedure on the LTE side, see Idle Mode Management
in eRAN Feature Documentation.
● The NR side does not involve cell reselection. Therefore, the NR side does not
broadcast the OSI. The gNodeB broadcasts MIB to enable UEs to obtain radio
frame timing.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 44


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

5.1.2 Paging
In NSA networking, the UE receives a paging message for originating services on
the LTE side, but does not receive any paging message on the NR side. For details
about the procedure on the LTE side, see Idle Mode Management in eRAN Feature
Documentation.

5.1.3 RA to the eNodeB


In NSA networking, the initial BWP information is carried in the
RRCConnectionReconfiguration message during RA to the eNodeB. The initial BWP
is controlled by the INIT_BWP_FULL_BW_SW option (selected by default) of the
NRDUCellAlgoSwitch.BwpConfigPolicySwitch parameter. Changing the setting
of this option will cause the cell to restart, affecting admitted UEs.
● When this option is selected, the gNodeB configures the full-bandwidth initial
BWP for all UEs.
● When this option is deselected, the gNodeB configures an initial BWP with the
bandwidth specified by CORESET#0 for all UEs, and configures the PRACH
frequency-domain position within the initial BWP. In this case, if the
frequency-domain position of the initial BWP is not at the edge of cell
frequency-domain resources, nor is the PRACH frequency-domain position.
This leads to discontinuous PUSCH RBs, affecting the uplink cell throughput.
For details about CORESET#0, see section 6.3.2 "Radio resource control
information elements" of 3GPP TS 38.331 V15.5.0.
For details about RA to the eNodeB in NSA networking, see Random Access
Control in eRAN Feature Documentation.

5.1.4 Signaling Connection Management


In NSA networking, before SgNB addition, signaling connections include an RRC
connection (signaling connection between the UE and eNodeB over the air
interface) and a dedicated S1 connection (signaling connection between the
eNodeB and MME). For details, see Connection Management in eRAN Feature
Documentation.

NOTE

During SgNB addition, signaling connections also include the X2 connection between the
eNodeB and gNodeB. For details, see 5.1.7 NG-RAN Radio Bearer Management.

5.1.5 E-UTRAN Radio Bearer Management


Before EN-DC setup, all user plane data is carried by the eNodeB. In this case,
radio bearer management involves only E-UTRAN. E-UTRAN radio bearer
management refers to SRB2 and DRB management by the eNodeB and involves
the setup, modification, and release of SRB2 and DRBs. For details, see Connection
Management in eRAN Feature Documentation.

5.1.6 NR B1 Measurement
In NSA networking, after a UE accesses the network from an eNodeB and selects a
neighboring NR cell with the best signal quality based on NR B1 measurement

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 45


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

results, the gNodeB serving the NR neighboring cell can work as the SgNB. Figure
5-2 shows the NR B1 measurement procedure.

Figure 5-2 NR B1 measurement procedure

1. The eNodeB sends an RRCConnectionReconfiguration message including the


NR B1 measurement configuration to the UE, requesting the UE to measure
neighboring NR cells.
2. The UE sends an RRCConnectionReconfigurationComplete message to notify
the eNodeB of the NR B1 measurement completion.
3. The UE sends a measurement report to the eNodeB. The measurement report
contains the NR B1 measurement result.

5.1.7 NG-RAN Radio Bearer Management


The gNodeB does not exchange signaling with the UE over the Uu interface. All
signaling exchanges between the gNodeB and the UE are forwarded over the X2
interface between the gNodeB and the eNodeB. Therefore, the signaling
connections on the NR side involve only X2 connections. After an X2 connection is
set up and the gNodeB receives an NR B1 measurement report from the UE, an
SgNB addition procedure can be triggered. For details about the SgNB addition
signaling procedure, see NSA Networking based on EPC.

NOTE

When the UE supports SRB3 and the NSA_DC_SRB3_SWITCH option of the


gNodeBParam.NsaDcOptSwitch parameter is selected, the gNodeB and UE can exchange
signaling using SRB3. For details, see NSA Networking based on EPC.

During the SgNB addition procedure, the MCG bearer is changed to MCG split
bearer or SCG split bearer.
● In Option 3, the eNodeB distributes the user plane data to the gNodeB and
itself, and the bearer is called the MCG split bearer.
● In Option 3x, the gNodeB distributes the user plane data to the eNodeB and
itself, and the bearer is called the SCG split bearer.
After EN-DC setup, radio bearer management involves NG-RAN. The NG-RAN
radio bearer management refers to SRB3 and DRB management by the gNodeB.
● SRB3 management by the gNodeB involves the setup and release of SRB3. For
details, see NSA Networking based on EPC.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 46


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

● DRB management by the gNodeB involves the setup, modification, and


release of DRBs. For details, see the following sections.

5.1.7.1 DRB Setup


A DRB can be set up after encryption and integrity protection are complete and
the UE context is created. DRB setup is triggered when the eNodeB sends an SgNB
Addition Request or SgNB Modification Request message. The
RRCConncetionReconfiguration message includes a drb-ToAddModList field in the
Radio Resource Config Dedicated IE. Upon receiving the message, the UE performs
the following operations:
● Sets up a PDCP entity and configures related security parameters.
● Sets up and configures an RLC entity.
● Sets up and configures a DTCH.
During SgNB addition, the eNodeB sends an SgNB Addition Request message to
the gNodeB, instructing the gNodeB to set up a DRB. Figure 5-3 shows the DRB
setup procedure.

Figure 5-3 DRB setup procedure

When a new data split bearer is set up after SgNB addition, the eNodeB sends an
SgNB Modification Request message to the gNodeB, instructing the gNodeB to set
up a DRB. Figure 5-4 shows the DRB setup procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 47


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-4 DRB setup procedure

5.1.7.2 DRB Modification


DRB modification is triggered when the eNodeB sends an SgNB Modification
Request message. Figure 5-5 shows the DRB modification procedure. According to
the instructions in an RRCConnectionReconfiguration message, the UE
reconfigures the PDCP entity, RLC entity, and DTCH.

Figure 5-5 DRB modification procedure

5.1.7.3 DRB Release


During a DRB release, the RRCConnectionReconfiguration message includes a drb-
ToReleaseList field in the Radio Resource Config Dedicated IE. Based on this
message, the UE releases all the resources related to the DRB. A DRB can be
released in the following scenarios:

● The eNodeB sends an SgNB Modification Request message. Figure 5-6 shows
the DRB release procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 48


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-6 DRB release procedure

● The eNodeB sends an SgNB Release Request message. Figure 5-7 shows the
DRB release procedure.

Figure 5-7 DRB release procedure

● The gNodeB sends an SgNB Release Required message. Figure 5-8 shows the
DRB release procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 49


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-8 DRB release procedure

5.1.8 RA to the gNodeB

5.1.8.1 RA Triggering Scenarios and RA Mechanisms


Table 5-1 describes RA triggering scenarios and RA mechanisms.

Table 5-1 RA triggering scenarios and RA mechanisms


Triggering Scenario Description Mechanism
Scenario

NSA access After a UE accesses an LTE cell, the Non-contention-based RA is


UE initiates RA in an NR cell upon the first choice. Contention-
the NR cell addition or change. based RA is used when
dedicated preambles of the
gNodeB are used up.

Handover During a handover, a UE initiates RA Non-contention-based RA is


in the target cell. the first choice. Contention-
based RA is used when
dedicated preambles of the
gNodeB are used up.

Downlink When a gNodeB needs to send Non-contention-based RA is


data downlink data to an preferentially used if the UE
arrival RRC_CONNECTED UE in an uplink reports the SSB index. In
out-of-synchronization state, the other scenarios, contention-
gNodeB instructs the UE to initiate based RA is used.
RA.

Uplink When an RRC_CONNECTED UE in Contention-based RA


data an uplink out-of-synchronization
transmissio state needs to send uplink data to a
n gNodeB, the UE initiates RA.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 50


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

5.1.8.2 RA Procedures
The contention-based RA procedure slightly differs from the non-contention-based
RA procedure. For details about RA procedures, see section 5.1 "Random Access
procedure" in 3GPP TS 38.321 V15.5.0.

5.1.8.2.1 Contention-based RA Procedure


Figure 5-9 shows how contention-based RA works.

Figure 5-9 Contention-based RA procedure

The contention-based RA procedure is as follows:


1. A UE sends an RA preamble.
The UE sends an RA preamble using Msg1. Figure 5-10 shows the RA
preamble transmission procedure.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 51


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-10 RA preamble transmission procedure

a. The UE obtains the PRACH configuration from RRCReconfiguration.


The UE obtains the time-frequency domain position for transmitting an
RA preamble based on the PRACH configuration.
b. The UE randomly selects an RA preamble with an even possibility.
Each SSB corresponds to a unique preamble index. Therefore, before
selecting an RA preamble, the UE first selects an SSB, and then
determines the RA preamble based on the SSB. The UE compares the
RSRP values of all SSBs in the cell with the RSRP threshold and selects an
SSB whose RSRP value is greater than the threshold. The RSRP threshold
is indicated by the rsrp-ThresholdSSB IE in 3GPP TS 38.331 V15.5.0 and
specified by the NRDUCellPrach.RsrpThldForSsbSelection parameter. If
no SSB meets the requirement, the UE selects an SSB randomly. For
details, see section 5.1.2 "Random Access Resource selection" in 3GPP TS
38.321 V15.5.0.
c. The UE sends the RA preamble.
2. The gNodeB sends an RA response.
3. The UE performs uplink scheduled transmission.
The UE determines the timing for scheduled transmission based on timing
alignment information. At least the C-RNTI of the UE is transmitted.
4. The gNodeB assists the UE in contention resolution.

5.1.8.2.2 Non-Contention-based RA Procedure


Figure 5-11 shows how non-contention-based RA works. Unlike contention-based
RA, non-contention-based RA does not involve contention resolution because RA
preambles are allocated by the gNodeB. Other procedures are the same between
non-contention-based RA and contention-based RA.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 52


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-11 Non-contention-based RA procedure

The non-contention-based RA procedure is as follows:

1. The gNodeB allocates an RA preamble to a UE.


When NR cells are added or changed, the gNodeB instructs the UE to initiate
RA through the RRCReconfiguration signaling, which carries the RA preamble
allocated to the UE. When allocating an RA preamble to a UE, the gNodeB
also indicates an SSB to the UE, through PDCCH or RRC signaling.
2. The UE sends the RA preamble.
Figure 5-12 shows the RA preamble transmission procedure.

Figure 5-12 RA preamble transmission procedure

a. The UE obtains the PRACH configuration from RRCReconfiguration or


PDCCH Order.
The UE obtains the time-frequency domain position for transmitting the
RA preamble based on the PRACH configuration.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 53


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

NOTE

After obtaining the PRACH configuration, the UE selects the SSB as indicated by
the gNodeB. For details, see section 5.1.2 "Random Access Resource selection" in
3GPP TS 38.321 V15.5.0.
● When selecting an SSB according to the PDCCH indication, the UE directly
selects the indicated SSB, and continues with the follow-up steps of the non-
contention-based RA procedure.
● When selecting an SSB according to the RRC signaling indication, the UE
needs to compare the RSRP value of the indicated SSB with the RSRP
threshold (corresponding to the rsrp-ThresholdSSB IE in 3GPP TS 38.331
V15.5.0 and specified by the NRDUCellPrach.RsrpThldForSsbSelection
parameter). If the RSRP value exceeds the threshold, the UE selects the
indicated SSB and continues with the follow-up steps of the non-contention-
based RA procedure. Otherwise, the UE initiates contention-based RA.
b. The UE sends the RA preamble.
3. The gNodeB sends an RA response.
When NR cells are added or changed, the RA response carries the RA-
preamble identifier and timing alignment information.
After the UE sends the RA preamble, it monitors the PDCCH within the RA
response window until an RA response is received.
– If the UE receives a response within the RA response window, the UE
considers the RA response successful. The UE proceeds with 4.
– If the UE does not receive a response within the RA response window, the
UE considers the RA response failed. In this case, if the number of RA
attempts is smaller than the upper limit (specified by the
NRDUCellPrach.MaxPreambleTransCnt parameter), the UE makes
another RA attempt. Otherwise, the RA procedure fails.
4. The UE performs uplink scheduled transmission.
The UE determines the timing for scheduled transmission based on timing
alignment information, and sends it to the gNodeB through Msg3.

5.1.8.3 RA Optimization
In the current version, RA optimization refers to optimized counter measurement
for contention-based RA.
During a contention-based RA procedure, if PRACH root sequence conflicts occur
between the serving cell and neighboring cells, a UE does not send a preamble
but the gNodeB may detect a preamble from the UE. This erroneous preamble
detection is considered a PRACH false alarm. For details about PRACH root
sequence conflict and PRACH false alarm, see Channel Management.
Table 5-2 describes the counters related to contention-based RA. PRACH false
alarms in the serving cell affect the measurement of the counters described in
Table 5-2, thereby impacting the RA success rate (indicated by the result of
N.RA.Contention.Resolution.Succ/N.RA.Contention.Att).

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 54


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Table 5-2 Counters related to contention-based RA


Counter ID Counter Name Counter Description

1911816542 N.RA.Contention.Att Number of random preamble


receptions

1911820708 N.RA.Contention.Resp Number of random preamble


responses

1911820710 N.RA.Contention.Msg3 Number of Msg3 receptions during


contention-based random access

1911816544 N.RA.Contention.Resoluti Number of successful contention


on.Succ resolutions

Optimized counter measurement for contention-based RA is introduced to reduce


the impact of PRACH false alarms caused by root sequence conflicts on the
measurement of the counters described in Table 5-2. In NSA networking, if root
sequence conflicts occur during an RA procedure triggered on the gNodeB side,
and the number of RA times is small, enabling this function will decrease the
measured values of counters related to contention-based RA and increase the RA
success rate. This function takes effect only in low frequency bands.
Optimized counter measurement for contention-based RA is enabled by selecting
the NSA_CBRA_STATISTICS_OPT_SW option of the
gNBOamParam.StatisticsStrategySwitch parameter. It is recommended that this
function be enabled when the root sequence conflict probability is high and the
number of RA times is small. When the number of RA times is large, the measured
values of counters related to contention-based RA slightly decrease or remain
unchanged, and the RA success rate slightly increases or remains unchanged.
When an SUL cell/a hyper cell exists, the increase in RA success rate may decrease
after this function is enabled.
After this function takes effect, the gNodeB triggers a timer with the same length
as the T304 timer when an RA procedure is triggered. Counters related to
contention-based RA are measured within the timer length. For details about
timer triggering scenarios, see descriptions of counters in Table 5-2 in
gNodeBFunction Performance Counter Summary.
Figure 5-13 shows an SgNB addition procedure where a timer is triggered. The
gNodeB triggers a timer with the same length as the T304 timer at point B. In this
case, the measurement of counters related to contention-based RA starts at point
A and ends when the timer triggered at point B expires.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 55


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

Figure 5-13 SgNB addition procedure

After this function is enabled, if the measured values of the counters described in
Table 5-2 (mainly the N.RA.Contention.Att and N.RA.Contention.Resp counters)
decrease, this function has taken effect.

5.2 Network Analysis

5.2.1 Benefits
The functions described in this chapter are basic functions in NSA networking and
are enabled by default along with cell activation.

5.2.2 Impacts

Network Impacts
None

Function Impacts
None

None

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 56


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

RAT Function Function Reference Description


Name Switch

Low- Low HIGH_RELIABI URLLC The full-bandwidth initial BWP is


frequency latency LITY_BASIC_S recommended when uplink
TDD and high W option of interference randomization-based
reliability the scheduling is enabled for fixed
NRDUCellAlgo resources of high-reliability services.
Switch.HighRe
liabilitySwitch
parameter

5.3 Requirements

5.3.1 Licenses
None

5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.

Prerequisite Functions
RAT Function Function Reference Description
Name Switch

FDD PDCCH AGG_LVL_INIT_ Channel The PDCCH aggregation level initial


Low- aggregati SELECT_OPT_S Management selection optimization function must
frequency on level W option of be enabled before the full-bandwidth
TDD initial the initial BWP configuration function
selection NRDUCellPdcc (specified by the
High- optimizat h.PdcchAlgoEn INIT_BWP_FULL_BW_SW option of
frequency ion hSwitch the
TDD parameter NRDUCellAlgoSwitch.BwpConfigPol
icySwitch parameter) and PDCCH
rate matching function (specified by
the PDCCH_RATEMATCH_SW option
of the
NRDUCellPdsch.RateMatchSwitch
parameter) are both enabled.

Mutually Exclusive Functions


None

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 57


5G RAN
5G Networking and Signaling Feature Parameter
Description 5 Basic Signaling Procedures in NSA Networking

5.3.3 Hardware
Base Station Models
3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Boards
All NR-capable main control boards and baseband processing units support this
function. To learn which main control boards and baseband processing units are
NR-capable, see the related BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.

RF Modules
All NR-capable RF modules support this function. For details about NR-capable RF
modules, see technical specifications of the related RF modules in 3900 & 5900
Series Base Station Product Documentation.

5.4 Operation and Maintenance


The basic NSA networking functions described in this chapter are enabled by
default along with cell setup. For details about cell setup in NSA networking, see
Cell Management.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 58


5G RAN
5G Networking and Signaling Feature Parameter
Description 6 Parameters

6 Parameters

The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE

You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.

FAQ: How do I find the parameters related to a certain feature from


parameter reference?

Step 1 Open the EXCEL file of parameter reference.


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

----End

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 59


5G RAN
5G Networking and Signaling Feature Parameter
Description 7 Counters

7 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE

You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from


performance counter reference?

Step 1 Open the EXCEL file of performance counter reference.


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

----End

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 60


5G RAN
5G Networking and Signaling Feature Parameter
Description 8 Glossary

8 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 61


5G RAN
5G Networking and Signaling Feature Parameter
Description 9 Reference Documents

9 Reference Documents

● 3GPP TS 33.501: "Security architecture and procedures for 5G System"


● 3GPP TR 38.801: "Study on new radio access technology: Radio access
architecture and interfaces"
● 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description"
● 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
● 3GPP TS 38.321: "NR;Medium Access Control (MAC) protocol specification"
● 3GPP TS 38.304: "NR;User Equipment (UE) procedures in Idle mode and RRC
Inactive state"
● 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)"
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Cell Management
● NSA Networking based on EPC
● Channel Management
● High Speed Mobility
● eXn Self-Management
● Feature parameter description documents in eRAN Feature Documentation:
– Idle Mode Management
– Random Access Control
– Connection Management
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation
● URLLC

Issue 02 (2021-04-30) Copyright © Huawei Technologies Co., Ltd. 62

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy