Basic SA Networking Functions (5G RAN2.1 - 01)

5G RAN
Basic SA Networking Functions

Feature Parameter Description
Issue 01
Date 2019-06-06
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

5G RAN
Basic SA Networking Functions Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 5G RAN2.1 01 (2019-06-06)..........................................................................................................................................1
1.2 5G RAN2.1 Draft E (2019-05-10)..................................................................................................................................1
1.3 5G RAN2.1 Draft D (2019-04-10)................................................................................................................................. 2
1.4 5G RAN2.1 Draft C (2019-03-18)................................................................................................................................. 2
1.5 5G RAN2.1 Draft B (2019-02-22)................................................................................................................................. 3
1.6 5G RAN2.1 Draft A (2018-12-30)................................................................................................................................. 4
2 About This Document.................................................................................................................. 5

2.1 General Statements......................................................................................................................................................... 5
2.2 Features in This Document.............................................................................................................................................5
3 Overview......................................................................................................................................... 7
4 Principles.......................................................................................................................................10
4.1 System Information Broadcast..................................................................................................................................... 10
4.1.1 System Information Block Contents..........................................................................................................................10
4.1.2 System Information Scheduling Periods....................................................................................................................11
4.1.3 System Information Update.......................................................................................................................................12
4.2 Paging........................................................................................................................................................................... 13
4.2.1 Triggering of Paging..................................................................................................................................................13
4.2.2 Paging Mechanism over the Uu Interface................................................................................................................. 13
4.3 RA.................................................................................................................................................................................15
4.3.1 Introduction to RA.....................................................................................................................................................15
4.3.2 RA Preambles............................................................................................................................................................ 16
4.3.2.1 Overview................................................................................................................................................................ 16
4.3.2.2 Preamble Sequence Generation.............................................................................................................................. 18
4.3.2.3 Preamble Sequence Grouping................................................................................................................................ 18
4.3.3 Time-Frequency Resources for RA........................................................................................................................... 19
4.3.4 RA Procedures........................................................................................................................................................... 22
4.3.4.1 Contention-based RA Procedure............................................................................................................................ 22
4.3.4.2 Non-Contention-based RA Procedure.................................................................................................................... 24
4.4 Signaling Connection Management..............................................................................................................................26
4.4.1 RRC Connection Setup..............................................................................................................................................27
4.4.2 Dedicated NG-C Connection Setup...........................................................................................................................28
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

5G RAN
Description Contents
4.4.3 RRC Connection Management.................................................................................................................................. 30

4.4.3.1 Uplink Out-of-Synchronization Management........................................................................................................ 30
4.4.3.2 UE Inactivity Management.....................................................................................................................................31
4.4.4 RRC Connection Reestablishment............................................................................................................................ 31
4.4.5 Signaling Connection Release................................................................................................................................... 33
4.5 Radio Bearer Management........................................................................................................................................... 34
4.5.1 SRB2 Setup................................................................................................................................................................34
4.5.2 SRB2 Modification....................................................................................................................................................34
4.5.3 SRB2 Release............................................................................................................................................................ 35
4.5.4 DRB Setup................................................................................................................................................................. 35
4.5.5 DRB Modification..................................................................................................................................................... 36
4.5.6 DRB Release..............................................................................................................................................................36
5 Network Analysis........................................................................................................................ 37
5.1 Benefits......................................................................................................................................................................... 37
5.2 Impacts..........................................................................................................................................................................37
6 Requirements............................................................................................................................... 38
6.1 Licenses........................................................................................................................................................................ 38
6.2 Software........................................................................................................................................................................38
6.3 Hardware...................................................................................................................................................................... 38
6.4 Others............................................................................................................................................................................39
7 Operation and Maintenance......................................................................................................40

8 Parameters..................................................................................................................................... 41
9 Counters........................................................................................................................................ 42
10 Glossary....................................................................................................................................... 43
11 Reference Documents............................................................................................................... 44
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

5G RAN
Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical Changes
Changes in functions and their corresponding parameters
l Editorial Changes
Improvements or revisions to the documentation
1.1 5G RAN2.1 01 (2019-06-06)

This issue introduces the following changes to 5G RAN2.1 Draft E (2019-05-10).
Technical Changes
Change Description Parameter Change Base Station Model
Optimized the dedicated None l 3900 and 5900 series

NG-C connection setup base stations
procedure. Integrity l DBS3900 LampSite and
protection and encryption DBS5900 LampSite
are performed before UE
capability query. For details,
see 4.4.2 Dedicated NG-C
Connection Setup.
Editorial Changes
Revised descriptions in this document.
1.2 5G RAN2.1 Draft E (2019-05-10)

This issue introduces the following changes to 5G RAN2.1 Draft D (2019-04-10).
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

5G RAN
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.3 5G RAN2.1 Draft D (2019-04-10)

This issue introduces the following changes to 5G RAN2.1 Draft C (2019-03-18).
Technical Changes
None
Editorial Changes
Updated the document None l 3900 and 5900 series

based on the product base stations
implementation. The l DBS3900 LampSite and
preamble format and the DBS5900 LampSite
number of PRBs occupied
by the PRACH, which are
not supported currently, are
now removed. For details,
see 4.3.2.1 Overview and
4.3.3 Time-Frequency
Resources for RA.
1.4 5G RAN2.1 Draft C (2019-03-18)

This issue introduces the following changes to Draft B (2019-02-22) of 5G RAN2.1.
Technical Changes
Added support for this None l 3900 series base stations

feature by 3900 series base l DBS3900 LampSite
stations and DBS3900
LampSite.

5G RAN
Modified the configuration Added parameters: l 3900 and 5900 series

parameters of the logical l NRDUCell.LogicalRoot base stations
root sequence index and SequenceIndex l DBS3900 LampSite and
start frequency-domain DBS5900 LampSite
position of the PRACH. For l NRDUCell.PrachFreqSt
details, see 4.3.2.2 artPosition
Preamble Sequence Deleted parameters:
Generation and 4.3.3 Time- l NRDUCellPrach.RootS
Frequency Resources for equenceIndex
RA.
l NRDUCellPrach.Prach
FreqStartPosition
Deleted the parameter of the Deleted parameter: l 3900 and 5900 series
maximum number of RLC gNBRlcParamGroup.UeM base stations
retransmissions due to no axAmRetransNum l DBS3900 LampSite and
configuration scenarios. For DBS5900 LampSite
details, see 4.4.4 RRC
Connection
Reestablishment.
Editorial Changes
None
1.5 5G RAN2.1 Draft B (2019-02-22)

This issue introduces the following changes to 5G RAN2.1 Draft A (2018-12-30).
Technical Changes
Added the function of Added parameter: l 5900 series base stations

configuring the proportion NRDUCellPrach.CbraPrea l DBS5900 LampSite
of random preamble mblePct
sequences to random
preamble sequences and
dedicated preamble
sequences. For details, see
4.3.2.3 Preamble Sequence
Grouping.

5G RAN

configuring the maximum NRDUCellPrach.MaxPrea l DBS5900 LampSite
number of RA attempts in mbleTransCnt
the contention-based RA
procedure. For details, see
4.3.4.1 Contention-based
RA Procedure.

configuring the RSRP NRDUCellPrach.RsrpThld l DBS5900 LampSite
threshold for the UE to ForSsbSelection
select the SSB in the
contention-based RA
procedure and non-
contention-based RA
procedure. For details, see
4.3.4.1 Contention-based
RA Procedure and 4.3.4.2
Non-Contention-based RA
Procedure.
Editorial Changes
None
1.6 5G RAN2.1 Draft A (2018-12-30)

This is the first release of this document.

5G RAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
l The technical principles of features and their related parameters
l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l 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.

5G RAN
Description 2 About This Document
Feature ID Feature Name Section
FBFD-021104 SA Option 2 Architecture 4.1 System Information Broadcast

4.2 Paging
4.3 RA
4.4 Signaling Connection Management
4.5 Radio Bearer Management

5G RAN
Description 3 Overview
3 Overview
SA networking uses the Option 2 architecture. It is an end-to-end 5G network architecture, in

which the terminals, NR air interface, and core network all adopt 5G standards. The purpose
is to support 5G interfaces and provide 5G functions and services.
Figure 3-1 shows the SA Option 2 network architecture.
Figure 3-1 SA Option 2 network architecture
The SA Option 2 network architecture includes the 5G Core Network (5GC) and NG Radio
Access Network (NG-RAN). The 5GC mainly provides the access and mobility management
function (AMF) and user plane function (UPF), while the NG-RAN consists of the gNodeB
and the UE. The following describes the interfaces between NEs:
l NG-C and NG-U: The gNodeB is connected to the AMF through the NG-C interface to
implement NG control plane functions. The gNodeB is connected to the UPF through the
NG-U interface to implement NG user plane functions.
l Xn-C and Xn-U: gNodeBs are connected through Xn-C and Xn-U interfaces to
implement Xn control plane and user plane functions, respectively.

5G RAN
l Uu: The gNodeB is connected to the UE through the Uu interface to implement NR air
interface functions.
Figure 3-2 shows the basic signaling process in SA networking.
Figure 3-2 Basic signaling process in SA networking
Basic SA networking functions include:

1. System information broadcast
The system information broadcast is the first step for a UE to obtain the basic network
service information. Through the system information broadcast process, the UE can
obtain basic access stratum (AS) and non-access stratum (NAS) information. For details,
see 4.1 System Information Broadcast.
2. Paging
The network finds UEs through paging. For details, see 4.2 Paging.
3. Random access (RA)
Random access is a necessary process to establish a radio link between the UE and the
network. For details, see 4.3 RA.
4. Signaling connection management
Signaling connections include an RRC signaling connection and a dedicated NG-C
signaling connection. For details, see 4.4 Signaling Connection Management.
5. Radio bearer management

5G RAN
The radio bearer management process is triggered by the setup, modification, and
deletion of the UE context or PDU session. For details, see 4.5 Radio Bearer
Management.

5G RAN
Description 4 Principles
4 Principles
4.1 System Information Broadcast

According to 3GPP TS 38.300, system information can be classified into minimum system
information (MSI) and other system information (OSI) by content.
l MSI includes the master information block (MIB) and system information block type 1
(SIB1).
– MIB: provides the UE with initial access information and information used to
capture SIB1. The gNodeB periodically broadcasts the MIB.
– SIB1: contains basic information required for initial accesses, including the initial
SSB-related information, initial bandwidth part (BWP) information, and downlink
channel configuration. The gNodeB periodically broadcasts SIB1.
l OSI includes SIB2 to SIBn. It contains information such as the mobility, earthquake and
tsunami warning system (ETWS), and commercial mobile alert system (CMAS). The
OSI can be broadcast periodically by the gNodeB, or sent by the gNodeB after the UE
initiates a subscription request. The current version supports only periodic broadcasting
of SIB2, SIB3, and SIB5.
4.1.1 System Information Block Contents

The MIB and each SIB contain different information, as listed in Table 4-1. For details, see
3GPP TS 38.331.
Table 4-1 Contents of the MIB and SIBs
Category Message Content
MSI MIB System frame number (SFN), subcarrier spacing (SCS) used by
SIB1, and SIB1 PDCCH configuration information
SIB1 Cell access and selection parameters, and system information

scheduling information
OSI SIB2 Parameters common to different types of cell reselection and

parameters dedicated to intra-frequency cell reselection

5G RAN
Category Message Content
SIB3 Intra-frequency neighboring cells and their reselection

parameters as well as blacklisted intra-frequency neighboring
cells
SIB5 Inter-RAT frequency list and reselection parameters of each

frequency used for cell reselection
4.1.2 System Information Scheduling Periods

System information is transmitted over the broadcast control channel (BCCH), which is a
logical channel, as shown in Figure 4-1.
Figure 4-1 System information delivery path
In Figure 4-1:
l The MIB is transmitted over the BCH. The scheduling period is 80 ms. The MIB is
updated every 80 ms. Within 80 ms, it can be repeatedly transmitted based on the
retransmission period. The BCH transport format is predefined. Therefore, the UE
receives the MIB without obtaining other information on the network.
l SIB1 is transmitted over the DL-SCH. The scheduling period is 160 ms. The SIB1 is
updated every 160 ms. Within 160 ms, it can be repeatedly transmitted based on the
retransmission period. After receiving the MIB, the UE receives the SIB1 according to
the configuration specified by the MIB.
l Other SIBs are encapsulated into system information and transmitted over the DL-SCH.
After receiving SIB1, the UE receives other SIBs according to the configuration
specified by SIB1.
Table 4-2 describes the scheduling period of each system information.

5G RAN
Table 4-2 System information scheduling periods
Category Sub- Channel Transmission Scheduling Retransmission

category Mode Period Period
MSI MIB BCCH > Periodic 80 ms It is 20 ms by

BCH > broadcast default and can
PBCH be configured by
the
NRDUCell.SsbP
eriod parameter.
SIB1 BCCH > Periodic 160 ms It is 20 ms by

DL-SCH broadcast default and can
> be configured by
PDSCH the
NRDUCell.Sib1
Period parameter.
OSI SIB2 BCCH > Periodic 320 ms No

DL-SCH broadcast retransmission
>
PDSCH
SIB3 BCCH > Periodic 320 ms No

>
PDSCH
SIB5 BCCH > Periodic 640 ms No

>
PDSCH
4.1.3 System Information Update

A UE reads the system information when the UE starts and camps on a cell, the UE reselects a
cell, a handover is complete, the UE enters NR-RAN from other RAT system, or the UE
returns to the coverage area again.
After correctly obtaining the system information, the UE does not repeatedly read it. It rereads
and updates system information only when any of the following conditions is met:
l The UE receives the system information change notification in the paging message
transmitted from the gNodeB.
l The UE receives the system information 3 hours after correctly receiving the previous
system information.
As described in 3GPP TS 38.331, the system information update process is limited within a
specific time window, which is defined as the BCCH modification period. The BCCH
modification period boundaries are defined by SFNs for which SFN mod m is 0. The BCCH
modification period starts at the time when the SFN meets the requirement of SFN mod m =
0. m is the number of radio frames comprising the BCCH modification period.

5G RAN
The UE receives the system information update indication through paging DCI. Then, it
receives the updated system information in the next BCCH modification period. Figure 4-2
shows the system information update procedure. In the figure, different colors indicate
different system information. After receiving the system information update indication in
modification period n, the UE receives the updated system information during modification
period n+1.
Figure 4-2 System information update procedure
BCCH modification period (m radio frames) = modificationPeriodCoeff x defaultPagingCycle
In the preceding formula:

l 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.
l defaultPagingCycle is the default paging cycle in units of radio frames. It is specified by
the NRDUCellPagingConfig.DefaultPagingCycle parameter.
NOTE
modificationPeriodCoeff and defaultPagingCycle are broadcast in SIB1.
When system information (except SIB6, SIB7, and SIB8) is updated, the gNodeB changes the
valueTag value in SIB1. The UE reads the value of valueTag and compares it with the one it
read last time. If the value has changed, the UE learns that the system information has
changed. The UE rereads and updates the system information. If the value has not changed,
the UE learns that the system information has not changed, and will not read the system
information. The UE reads system information again 3 hours after receiving the previous
system information. In this case, the UE reads all the system information regardless of
whether the value of valueTag has changed.
4.2 Paging
4.2.1 Triggering of Paging

The network finds UEs through paging. 5GC paging is triggered by the 5GC. When there is
downlink data to transmit to a UE in RRC_IDLE mode, the 5GC triggers paging for the UE.
The paging message is finally delivered by the gNodeB to the UE over the air interface.
4.2.2 Paging Mechanism over the Uu Interface

The paging message is transmitted over the PCCH, which is a logical channel, as shown in
Figure 4-3.

5G RAN
Figure 4-3 Paging message delivery path
As stipulated in 3GPP TS 38.304, each UE in the RRC_IDLE state receives a paging message
only at a fixed time-domain position over the air interface. The position is represented by a
paging frame (PF) and a paging occasion (PO), as shown in Figure 4-4.
l PF: a radio frame. It indicates the paging start frame and contains multiple complete
POs.
l PO: is a set of PDCCH monitoring occasions and consists of multiple slots. The length
of one PO is equal to one beam sweeping period (corresponding to multiple SSB beams),
and the paging messages sent on these SSB beams are the same. As stipulated in 3GPP
TS 38.321, a maximum of 32 UEs can be paged within a PO.

5G RAN
Figure 4-4 Paging mechanism
The formulas for the PF and PO are as follows:
l Formula for calculating the SFN of a PF: (SFN + PF_offset) mod T = (T div N) x
(UE_ID mod N)
l Formula for calculating the i_s of a PO: i_s = floor (UE_ID/N) mod Ns
The i_s of the PO indicates the start position of a set of PDCCH monitoring occasions.
The UE starts to receive paging messages from the i_sth PO.
In the preceding information:
l T: indicates the DRX cycle of the UE (also referred to as paging cycle).

l PF_offset: indicates the frame offset of the PF.
l N: indicates the number of PFs contained in the paging cycle T.
l UE_ID: indicates the ID of a UE.
l Ns: indicates the number of POs contained in a PF.
4.3 RA
4.3.1 Introduction to RA
RA is used to establish and recover the uplink synchronization between a UE and the
gNodeB. During RA, a UE attempting to access the network sends an access request to the
gNodeB, and the gNodeB responds to the request, allocating dedicated resources to the UE
for data transmissions.
Depending on whether contention is applied, RA can either be contention-based or non-

contention-based.
l Contention-based RA

5G RAN
Preambles are randomly selected by UEs, and conflicts may exist among these
preambles. The gNodeB uses a contention resolution mechanism to handle access
requests. The RA result is random and not all RA procedures succeed.
l Non-contention-based RA
Preambles are allocated by the gNodeB and such preambles are UE-dedicated.
Therefore, there is no preamble conflict. When dedicated resources are insufficient, the
gNodeB instructs UEs to initiate contention-based RA.
Table 4-3 describes RA triggering scenarios and RA mechanisms.
Table 4-3 RA triggering scenarios and RA mechanisms

Triggering Description RA Mechanism
Scenario
Initial RRC When a UE needs to change from Contention-based RA

connection setup RRC_IDLE mode to
RRC_CONNECTED mode, the UE
initiates RA to establish an RRC
connection.
RRC connection After detecting a radio link failure, Contention-based RA

reestablishment the UE initiates RA to reestablish an
RRC connection.
Handover During a handover, a UE initiates Non-contention-based RA is

RA in the target cell. the first choice. Contention-
based RA is used when
dedicated preambles are
used up.
Downlink data When a gNodeB needs to send Contention-based RA

arrival downlink data to a UE that is in
RRC_CONNECTED mode but has
lost uplink synchronization, the
gNodeB instructs the UE to initiate
RA.
Uplink data When a UE that is in Contention-based RA

transmission RRC_CONNECTED mode but has
lost uplink synchronization needs to
send uplink data to a gNodeB, the
UE initiates RA.
4.3.2 RA Preambles
4.3.2.1 Overview
During RA, a UE needs to send an RA preamble on the PRACH (the sent signal is a
preamble). RA preamble formats fall into two types: long format and short format. An RA
preamble is a pulse signal, which consists of a TCP, a TSEQ, and a TGT in the time domain, as

5G RAN
shown in Figure 4-5. TCP denotes a cyclic prefix, TSEQ a preamble sequence, and TGT the
guard time. In the frequency domain, the RA preamble uses multiple subcarriers, specifically
839 subcarriers for a long preamble and 139 subcarriers for a short preamble.
Figure 4-5 RA preamble format
Table 4-4 and Table 4-5 list the mapping among format indexes, preamble length ( ), and
PRACH SCS ( ) supported by Huawei in the current version. For details about
preambles in all formats defined in 3GPP specifications, see section 6.3.3.1 "Sequence
generation" in 3GPP TS 38.211.
Table 4-4 Long preamble

Format
0 839 1.25 kHz
Table 4-5 Short preamble

Format
C2 139 kHz
In this version, the preamble format and PRACH SCS used by the gNodeB are determined by
the duplex mode (NRDuCell.DuplexMode), uplink-downlink subframe configuration
(NRDuCell.SlotAssignment), PUSCH subcarrier spacing (NRDuCell.SubcarrierSpacing),
cell radius (NRDuCell.CellRadius), and PRACH configuration index
(NRDUCellPrach.PrachConfigurationIndex), as listed in Table 4-6.

5G RAN
Table 4-6 Preamble format and PRACH SCS used by the gNodeB
Duplex UL-DL PUSCH Cell Radius PRACH Preamble PRACH
Mode Subframe SCS Config Index Format SCS
Config
CELL_FDD N/A 15 kHz ≤ 14.5 km 0–21, 65535 0 1.25 kHz
CELL_TDD 4_1_DDDS 30 kHz ≤ 9.65 km 200, 202, 210, C2 15 kHz

U 65535
CELL_TDD 8_2_DDDD 30 kHz ≤ 14.5 km 0–7, 12, 17, 0 1.25 kHz

DDDSUU 65535
or
7_3_DDDS
UDDSUU
CELL_TDD 8_2_DDDD 30 kHz ≤ 9.65 km 200, 202, 210 C2 15 kHz

DDDSUU
or
7_3_DDDS
UDDSUU
CELL_SUL N/A 15 kHz ≤ 14.5 km 0–21, 65535 0 1.25 kHz
4.3.2.2 Preamble Sequence Generation

Preamble sequences are generated through cyclic shifts of ZC root sequences.
l The logical ZC root sequence index is specified by the

NRDUCell.LogicalRootSequenceIndex parameter. For a long preamble, the parameter
value cyclically ranges from 0 to 837. For a short preamble, the parameter value
cyclically ranges from 0 to 137. For example,
– For a long preamble, logical index 837 is followed by index 0.
– For a short preamble, logical index 137 is followed by index 0.
l The number of cyclic shifts is determined by the gNodeB based on the cell type and
radius.
Each cell can be configured with a maximum of 64 preambles. If less than 64 preamble
sequences are generated from a single ZC root sequence, subsequent ZC root sequences are
used until 64 preambles are generated. For details about preamble sequence generation, see
section 6.3.3.1 "Sequence generation" in 3GPP TS 38.211 V2.0.0. The logical ZC sequence
index and the number of cyclic shifts are indicated by the RACH-ConfigCommon IE.
NOTE
In SA networking, the RACH-ConfigCommon IE is carried in SIB1. In NSA networking, the RACH-

ConfigCommon IE is carried in the RRCConnectionReconfiguration message.
4.3.2.3 Preamble Sequence Grouping

Based on the contention mechanism used during RA, 64 preamble sequences of a cell are
grouped into random preamble sequences and dedicated preamble sequences, as shown in

5G RAN
Figure 4-6. The proportion of random preamble sequences to random and dedicated preamble
sequences can be configured by using the NRDUCellPrach.CbraPreamblePct parameter.
l If this parameter is set to a value other than 255, the proportion of random preamble
sequences is the value of this parameter.
l If this parameter is set to 255, the proportion of random preamble sequences is 82%.
NOTE
Random preambles are used for contention-based RA. For details, see 4.3.4.1 Contention-based RA
Procedure. Dedicated preambles are used for non-contention-based RA. For details, see 4.3.4.2 Non-
Contention-based RA Procedure.
The number of random preambles varies with RA scenarios and is indicated by the
totalNumberOfRA-Preambles parameter in the RACH-ConfigCommon IE. For details, see
section 6.3.2 "Radio resource control information elements" in 3GPP TS 38.331 V2.0.0.
Figure 4-6 Preamble sequence grouping
4.3.3 Time-Frequency Resources for RA

A UE initiates RA using specific time-frequency resources (namely, PRACH). When a UE
initiates an access request over the PRACH, a preamble is transmitted.
Time-Domain Position
The time-domain position of a PRACH refers to the frame number and slot number of a
preamble. The frame number and slot number are determined by the PRACH configuration
index. For details, see section 6.3.3.2 "Mapping to physical resources" in 3GPP TS 38.211
V2.0.0. The PRACH configuration index used by the gNodeB is specified by the
NRDuCellPrach.PrachConfigurationIndex parameter.
l If this parameter is not set to 65535, the PRACH configuration index used by the
gNodeB is the value of this parameter.
l If this parameter is set to 65535, the PRACH configuration index used by the gNodeB is
automatically generated by the gNodeB based on the frequency, duplex mode
(NRDuCell.DuplexMode), uplink-downlink subframe configuration
(NRDuCell.SlotAssignment), PUSCH subcarrier spacing

5G RAN
(NRDuCell.SubcarrierSpacing), and cell radius (NRDuCell.CellRadius). Table 4-7

lists the PRACH configuration indexes that can be used by the gNodeB in this version.
Table 4-7 PRACH configuration indexes that can be used by the gNodeB when the PRACH configuration index
parameter is set to 65535
Duplex Mode UL-DL Subframe PUSCH SCS Cell Radius PRACH Configuration
Configuration Index
CELL_FDD N/A 15 kHz ≤ 14.5 km 19
CELL_TDD 4_1_DDDSU 30 kHz ≤ 9.65 km 202
CELL_TDD 8_2_DDDDDDDS 30 kHz ≤ 14.5 km 17

UU or
7_3_DDDSUDDS
UU
CELL_SUL N/A 15 kHz ≤ 14.5 km l SA networking: 19

l NSA networking: 21
l NSA+SA networking:
21
Frequency-Domain Position
The start frequency-domain position of a PRACH is specified by the
NRDUCell.PrachFreqStartPosition parameter.
l If this parameter is not set to 65535, the start frequency-domain position of the PRACH
is the Xth RB of the initial BWP where X is the value of this parameter.
l If this parameter is set to 65535, the PRACH is located at the low frequency band of the
initial BWP. When a long PUCCH is configured in the initial BWP bandwidth, the
PRACH is adjacent to the long PUCCH. When a long PUCCH is not configured, the
PRACH is adjacent to a common PUCCH, as shown in Figure 4-7.

5G RAN
Figure 4-7 Frequency-domain position of a PRACH
A PRACH occupies multiple PRBs in the frequency domain. The number of PRBs is related
to the preamble length ( ), PRACH SCS ( ), and PUSCH SCS ( ). Table 4-8 lists
the number of PRBs supported by Huawei in the current version. For details about all the
numbers of PRBs defined in 3GPP specifications, see section 6.3.3.2 "Mapping to physical
resources" in 3GPP TS 38.211.

5G RAN
Table 4-8 Number of PRBs for a PRACH
for a PUSCH Number of PRBs

for a PRACH
for a PRACH
839 1.25 kHz 15 kHz 6
839 1.25 kHz 30 kHz 3
139 15 kHz 30 kHz 6
4.3.4 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.
4.3.4.1 Contention-based RA Procedure

Figure 4-8 shows how contention-based RA works.
Figure 4-8 Contention-based RA
NOTE
The UE selects an SSB before sending the RA preamble. It needs to compare the RSRP of all the SSBs
in the cell with the RSRP threshold (corresponding to the rsrp-ThresholdSSB IE in 3GPP TS 38.331 and
specified by the NRDUCellPrach.RsrpThldForSsbSelection parameter). The UE selects an SSB whose
RSRP is greater than the threshold. If no SSB meets the requirements, the UE selects an SSB randomly.
For details, see section "Random Access Resource selection" in 3GPP TS 38.321.
RA Preamble
Figure 4-9 shows how an RA preamble is transmitted during contention-based RA.

5G RAN
Figure 4-9 RA preamble transmission
RA Response
Upon receiving a preamble, the gNodeB applies for a temporary cell radio network temporary
identifier (C-RNTI) and uplink and downlink scheduling resources.
Then, the gNodeB sends an RA response over the PDSCH. The response contains the RA-
preamble identifier, timing alignment information, initial uplink grant, and temporary C-
RNTI. One PDSCH can carry RA responses to multiple UEs at the same time.
After the UE sends a preamble, it monitors the PDCCH and waits for an RA response within
the RA response window:
l 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 then transmits uplink scheduling information.
l 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.
Uplink Scheduled Transmission

The UE sends uplink scheduling information over the PUSCH. The signaling messages and
information sent by the UE vary across different RA scenarios:
l Initial RRC connection setup

5G RAN
The RRCSetupRequest message (carrying NAS UE_ID) is transmitted over the common
control channel (CCCH) in TM mode at the RLC layer. The message is not segmented.
l RRC connection reestablishment
The RRCReestablishmentRequest message (not carrying the NSA message) is
transmitted over the CCCH in TM at the RLC layer. The message is not segmented.
l Handover
Contention-based RA, instead of non-contention-based RA, is triggered if the UE
accesses the target cell and no dedicated preambles are available during a handover.
The RRC Handover Confirm message and C-RNTI are transmitted over the dedicated
control channel (DCCH). If required, a buffer status report (BSR) is also carried.
l Other scenarios
At least the C-RNTI of the UE is transmitted.
Contention Resolution
After the UE sends Msg3 (see Figure 4-8), 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.
l The UE keeps monitoring the PDCCH before the timer expires and considers the
contention resolution successful and stops the timer if either of the following conditions
is met:
– The UE obtains the C-RNTI over the PDCCH.
– The UE obtains the temporary C-RNTI over the PDCCH and the MAC packet data
unit (PDU) is successfully decoded. Specifically, the UE Contention Resolution
Identity IE received over the PDSCH is the same as that carried in Msg3 sent by the
UE.
l If the contention resolution timer expires, the UE 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.3.4.2 Non-Contention-based RA Procedure

Figure 4-10 shows the non-contention-based RA process. 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.

5G RAN
Figure 4-10 Non-contention-based RA
NOTE
When allocating an RA preamble to a UE, the gNodeB also indicates an SSB, provided by either
PDCCH or RRC, to the UE. Before sending the RA preamble, the UE selects an SSB, as indicated by
the gNodeB. For details, see section "Random Access Resource selection" in 3GPP TS 38.321.
l When the UE selects an SSB according to the PDCCH indication, the UE directly selects the
indicated SSB, and continues to complete follow-up steps of the non-contention-based RA
procedure.
l When the UE selects an SSB according to the RRC signaling indication, the UE needs to compare
the RSRP of the indicated SSB with the RSRP threshold (corresponding to the rsrp-ThresholdSSB
IE of 3GPP TS 38.331 and specified by the NRDUCellPrach.RsrpThldForSsbSelection
parameter). If the RSRP exceeds the threshold, the UE selects the indicated SSB and continues to
complete follow-up steps of the non-contention-based RA procedure. Otherwise, the UE initiates
contention-based RA.
The non-contention-based RA process is as follows:

1. The gNodeB allocates an RA preamble to the UE.
– During a handover, the MobilityControlInfo IE sent by the source gNodeB carries
the allocated preamble.
– When NR cells are added in NSA networking, the gNodeB instructs the UE to
initiate RA through the RRCReconfiguration signaling, which carries the allocated
preamble.
2. The UE sends an RA preamble.
Figure 4-11 shows how an RA preamble is transmitted.

5G RAN
Figure 4-11 RA preamble transmission
3. The gNodeB sends an RA response.

– During a handover, the RA response must contain the timing alignment information
and initial uplink grant.
– When NR cells are added in NSA networking, the RA response must contain the
timing alignment information and RA preamble identifier.
After the RA response is successful, the non-contention-based RA procedure is complete
and the UE performs uplink scheduled transmission.
4. The UE performs uplink scheduled transmission.
The UE transmits uplink scheduling information (containing at least the C-RNTI of the
UE) over the PUSCH.
4.4 Signaling Connection Management

Signaling connections include an RRC connection and a dedicated NG-C connection, as
shown in Figure 4-12. Generally, a signaling connection is set up for a service bearer. It can
also be set up for a signaling procedure, such as a UE location update.

5G RAN
Figure 4-12 Signaling connection protocol stack
Signaling connection management involves RRC connection setup, dedicated NG-C

connection setup, RRC connection management, RRC connection reestablishment, and
signaling connection release.
4.4.1 RRC Connection Setup

During RRC connection setup, SRB1 is set up, as shown in Figure 4-13.
Figure 4-13 RRC connection setup procedure
1. The UE sends Msg1 to the gNodeB to initiate a random access procedure.

2. The gNodeB sends Msg2 to the UE to allocate the time-domain and frequency-domain
resources of Msg3.

5G RAN
3. The UE sends an RRCSetupRequest message carrying the RRC connection setup cause
and UE identity to the gNodeB.
NOTE
l The RRC connection setup cause is specified by the upper layer.

l The UE identity can be the S-TMSI or a random number.
l If the upper layer provides the S-TMSI, the message contains the S-TMSI.
l If no 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.
NOTE
If the admission or resource allocation fails, the gNodeB responds to the UE with an RRCReject
message. The RRC connection setup fails.
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, and then sends an RRCSetupComplete message to the gNodeB.
The RRC connection setup completes.
After the gNodeB sends the RRCSetup message, it starts a timer to wait for the
RRCSetupComplete message. The timer is specified by the
gNBConnStateTimerUuMessageWaitingTimer parameter. If the gNodeB does not
receive the RRCSetupComplete message from the UE after the timer expires, the RRC
connection setup fails.
4.4.2 Dedicated NG-C Connection Setup

Figure 4-14 shows the dedicated NG-C connection setup procedure.

5G RAN
Figure 4-14 Dedicated NG-C connection setup procedure
1. After the RRC connection is set up, the UE sends an RRCSetupComplete message
carrying the selectedPLMN-Identity, registeredAMF, s-nssai-list, and NAS message to
the gNodeB.
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 InitialUeMessage.
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 InitialContextSetupReq message to the gNodeB to initiate the initial
context setup procedure.
NOTE
l After security mode completion, the gNodeB sends a UECapabilityEnquiry message to the UE
to initiate a UE capability query procedure, as indicated by step 7 to step 9, only when the
InitialContextSetupReq message does not carry the UE Radio Capability IE. Otherwise, skip
step 7 to step 9.
l After UE capability query completion, the gNodeB sends an RRCReconfiguration message to
the UE, instructing it to set up SRB2 and DRB, as indicated by step 10 and step 11, only when
the InitialContextSetupReq message carries the PDU Session Resource Setup Request List IE.
Encryption and integrity protection have been performed for this RRCReconfiguration
message. Otherwise, skip step 10 and step 11.
5. The gNodeB sends a SecurityModeCommand message to the UE, instructing the UE to
start integrity protection and encryption. Then, downlink encryption starts.

5G RAN
6. Based on the integrity protection and encryption algorithms indicated by the

SecurityModeCommand message, the UE generates the 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 sends a UECapabilityInfolnd message to the AMF to transparently transmit
the UE capability information.
10. The gNodeB sends an RRCReconfiguration message to the UE, instructing it to set up
SRB2 and DRB.
11. After receiving the RRCReconfiguration message, the UE starts the setup of SRB2 and
DRB. After the setup is successful, the UE sends an RRCReconfigurationComplete
message to the gNodeB.
12. The gNodeB sends an InitialContextSetupRsp message to the AMF.
4.4.3 RRC Connection Management

A gNodeB detects the status of the uplink radio links for the management of UEs in
RRC_CONNECTED mode. The following mechanisms have been implemented:
l Uplink out-of-synchronization management: enables a gNodeB to maintain uplink
timing for a UE in real time so that the UE remains in the uplink synchronization state.
l UE inactivity management: If a UE does not transmit or receive any user plane data
(excluding MAC CEs) within a specified period, the gNodeB releases the RRC
connection or initiates state transition for the inactive UE.
NOTE
A UE becomes inactive when it does not transmit or receive data within the specified period or
when it disconnects from the gNodeB.
4.4.3.1 Uplink Out-of-Synchronization Management

Uplink out-of-synchronization management enables a gNodeB to maintain uplink timing for a
UE in real time so that the UE remains in the uplink synchronization state.
During uplink out-of-synchronization management, the gNodeB sends a Timing Advance

Command message to the UE and receives an ACK reply from the UE to maintain uplink
timing. Each time the gNodeB receives an ACK reply from the UE, the gNodeB starts or
restarts the uplink time alignment timer specified by the
NRDUCellUlTaConfig.UlTimeAlignmentTimer parameter. If the timer expires, the gNodeB
considers the UE to have entered the out-of-synchronization state.
After the UE is in the uplink out-of-synchronization state:
l The gNodeB instructs the UE to initiate a random access procedure when the gNodeB
needs to transmit data to the UE.
l The UE initiates a random access procedure to restore uplink synchronization if it needs
to transmit data to the gNodeB.

5G RAN
4.4.3.2 UE Inactivity Management

After detecting inactive UEs, the gNodeB performs inactivity management on the UEs. This
prevents inactive UEs from occupying system resources for a long period.
When detecting that a UE is in any of the following situations, the gNodeB considers the UE
inactive.
l The gNodeB detects that the UE is in the signaling-only connection for more than 60
seconds.
l After the UE establishes a data bearer, the gNodeB detects that the UE does not transmit
or receive any data (excluding MAC CEs) for a period specified by the UE inactivity
timer (NRDUCellQciBearer.UeInactivityTimer).
After the UE becomes inactive, the gNodeB sends a UeContextReleaseReq message carrying
the release cause "User Inactivity" to the AMF to initiate an RRC connection release.
4.4.4 RRC Connection Reestablishment

RRC connection reestablishment is a service processing procedure initiated by the UE for
quick RRC connection setup. The UE can initiate an RRC connection reestablishment
procedure only when an RRC connection had been set up successfully and the security mode
had been successfully enabled. The UE triggers the RRC connection reestablishment
procedure in any of the following scenarios:
l A radio link failure (RLF) occurs.
A UE detects an RLF (for details, see 3GPP TS 38.331) when any of the following
conditions is met:
– The timer specified by the NRDUCellUeTimerConst.T310 parameter expires.
– Random access fails and the timer specified by the
NRDUCellUeTimerConst.T311 parameter is not running.
– The number of RLC retransmissions reaches the maximum.
l An inter-RAT outgoing handover fails.
l An intra-RAT handover fails.
l Integrity check fails.
l RRC connection reconfiguration fails.
Figure 4-15 shows the RRC connection reestablishment procedure.

5G RAN
Figure 4-15 RRC connection reestablishment procedure
1. The UE sends Msg1 to the gNodeB to initiate a random access procedure.

2. The gNodeB sends Msg2 to the UE to allocate the time-domain and frequency-domain
resources of Msg3.
3. The UE reestablishes SRB1 and sends an RRCReestablishmentRequest message
carrying the c-RNTI, physCellId, and shortMAC-I used before reestablishment to the
gNodeB.
4. After receiving the RRCReestablishmentRequest message, the gNodeB performs the
following:
a. Based on the c-RNTI, physCellId, and shortMAC-I, the gNodeB searches for the
UE context used 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.
5. The UE responds the gNodeB with an RRCSetupComplete message.

5G RAN
6. The gNodeB continues to reestablish the SRB2 and DRB.

7. The gNodeB sends an RRCReconfiguration message to the UE, instructing the UE to
reestablish the SRB2 and DRB.
8. The UE sends an RRCReconfigurationComplete message to the gNodeB. The RRC
connection reestablishment procedure is complete.
4.4.5 Signaling Connection Release

Signaling connection release consists of dedicated NG-C connection release and RRC
connection release. After an RRC connection is released, the signaling connection between
the UE and gNodeB, and all the involved radio bearers are released.
Figure 4-16 shows the signaling connection release procedure.
Figure 4-16 Signaling connection release procedure
A signaling connection release procedure can be triggered by the gNodeB or AMF.

l The gNodeB sends a UeContextReleaseReq message to the AMF upon detecting an
exception, such as the UE inactivity.
l The AMF sends a UeContextReleaseCmd message to the gNodeB when the AMF
decides to abort the service of the UE or the UE decides to abort the service and informs
the AMF through NAS signaling.
After the signaling connection release starts, the gNodeB:
1. Releases transport resources.
2. Sends an RRCRelease message to the UE, instructing the UE to release the RRC
connection.
3. Releases radio resources.
4. Sends a UeContextReleaseCmp message to the AMF, indicating that the resources are
released. After receiving the message, the AMF releases the NAS context information
corresponding to the UE.

5G RAN
5. Releases the AS context information corresponding to the UE. Then, the UE switches
from the connected mode to the idle mode.
4.5 Radio Bearer Management

The radio bearer management process is triggered by the setup, modification, and deletion of
the UE context or PDU session. The radio bearer management process is implemented by the
gNodeB and the UE through RRC reconfiguration. Radio bearers are classified into signaling
radio bearers (SRBs) and data radio bearers (DRBs).
l SRBs carry signaling in the control plane. There are three types of SRBs:
– SRB0: carries RRC signaling through a common control channel (CCCH) in
transparent mode (TM) at the radio link control (RLC) layer before the RRC
connection is successfully set up.
– SRB1: carries RRC signaling messages after the RRC connection is successfully set
up, and carries NAS messages prior to the establishment of SRB2. SRB1 is
transmitted through a dedicated control channel (DCCH) in acknowledged mode
(AM) at the RLC layer.
– SRB2: carries NAS signaling through a DCCH logical channel in AM mode at the
RLC layer. SRB2 has a lower priority than SRB1, and can be set up only after
security activation.
NOTE
l For details about SRB0, SRB1, and SRB2, see 3GPP TS 38.331.
l For details about NAS, see 3GPP TS 24.301.
l DRBs carry data in the user plane. A maximum of eight DRBs can be set up between a
UE and a gNodeB. The actual number depends on different QoS classes.
In this document, radio bearer management refers to SRB2 and DRB management by the
gNodeB after security activation. It involves the setup, modification, and release of SRB2 and
DRBs.
4.5.1 SRB2 Setup

After encryption and integrity protection are complete during dedicated NG-C connection
setup, the gNodeB instructs the UE to set up SRB2 based on the value of the srb-
ToAddModList IE in the RRCReconfiguration message. Upon receiving the message, the UE
performs the following operations:
l Sets up a PDCP entity and configures related security parameters.

l Sets up and configures an RLC entity.
l Sets up and configures a DCCH.
SRB2 setup uses the same procedure as dedicated NG-C connection setup. For details, see
4.4.2 Dedicated NG-C Connection Setup.
4.5.2 SRB2 Modification

Figure 4-17 shows the SRB2 modification procedure. The gNodeB sends the UE an
RRCReconfiguration message containing the srb-ToAddModList IE, instructing the UE to
reconfigure the PDCP entity, RLC entity, and DCCH.

5G RAN
Figure 4-17 SRB2 modification procedure
4.5.3 SRB2 Release

SRB2 is released during signaling connection release. In normal cases, SRB2 is released with
SRB1. For details, see 4.4.5 Signaling Connection Release.
4.5.4 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 AMF sends a PduSessionSetupReq
message. The RRCReconfiguration message includes a drb-ToAddModList field in the Radio
Resource Config Dedicated IE. Upon receiving the message, the UE performs the following
operations:
l Sets up a PDCP entity and configures related security parameters.

l Sets up and configures an RLC entity.
l Sets up and configures a DTCH.
Figure 4-18 shows the DRB setup procedure.
Figure 4-18 DRB setup procedure

5G RAN
4.5.5 DRB Modification

A DRB can be modified by the AMF using a PduSessionModifyReq message. Figure 4-19
shows the DRB modification procedure. According to the instructions in an
RRCReconfiguration message, the UE reconfigures the PDCP entity, RLC entity, and DTCH.
Figure 4-19 DRB modification procedure
4.5.6 DRB Release

A DRB can be released by the AMF using a PduSessionReleaseReq command or released in a
signaling connection release procedure. Figure 4-20 shows the DRB release procedure.
During a DRB release, the RRCReconfiguration 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.
Figure 4-20 DRB release procedure

5G RAN
Description 5 Network Analysis
5 Network Analysis
5.1 Benefits
The functions described in this document are basic functions in SA networking and are
enabled by default along with cell activation.
5.2 Impacts
Network Impacts
None
Function Impacts
None

5G RAN
Description 6 Requirements
6 Requirements
6.1 Licenses
None
6.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
None
Mutually Exclusive Functions

None
6.3 Hardware
Base Station Models
l 3900 and 5900 series base stations. 3900 series base stations must be configured with the
BBU3910.
l 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 BBU5900
Hardware Description or 3900 Series BBU Hardware Description.

5G RAN
Description 6 Requirements
RF Modules
All NR-capable AAUs/RRUs/pRRUs support this feature.
l For details about NR-capable AAUs, see AAU Technical Specifications.
l For details about NR-capable RRUs, see RRU Technical Specifications.
l For details about NR-capable pRRUs, see LampSite pRRU&RRU Technical
Specifications.
6.4 Others
None

5G RAN
Description 7 Operation and Maintenance
7 Operation and Maintenance
The basic SA networking functions described in this document are enabled by default along
with cell setup. For details about cell setup in SA networking, see Cell Management.

5G RAN
Description 8 Parameters
8 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l 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 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.

5G RAN
Description 9 Counters
9 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l 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.

5G RAN
Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

5G RAN
Description 11 Reference Documents
11 Reference Documents
l 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description"

l 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
l 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System
(EPS)"
l 3GPP TS 38.211: "NR; Physical channels and modulation"
l Cell Management
l BBU5900 Hardware Description
l 3900 Series BBU Hardware Description
l AAU Technical Specifications
l RRU Technical Specifications
l LampSite pRRU&RRU Technical Specifications

Basic SA Networking Functions (5G RAN2.1 - 01)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Basic SA Networking Functions (5G RAN2.1 - 01)

Caricato da

Copyright:

Formati disponibili

5G RAN

Basic SA Networking Functions

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

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

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

4.4.3 RRC Connection Management.................................................................................................................................. 30

7 Operation and Maintenance......................................................................................................40

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

1.1 5G RAN2.1 01 (2019-06-06)

Optimized the dedicated None l 3900 and 5900 series

1.2 5G RAN2.1 Draft E (2019-05-10)

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

1.3 5G RAN2.1 Draft D (2019-04-10)

Updated the document None l 3900 and 5900 series

1.4 5G RAN2.1 Draft C (2019-03-18)

Added support for this None l 3900 series base stations

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter Change Base Station Model

Modified the configuration Added parameters: l 3900 and 5900 series

1.5 5G RAN2.1 Draft B (2019-02-22)

Added the function of Added parameter: l 5900 series base stations

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Change Base Station Model

Added the function of Added parameter: l 5900 series base stations

Added the function of Added parameter: l 5900 series base stations

1.6 5G RAN2.1 Draft A (2018-12-30)

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 4

2 About This Document

2.1 General Statements

2.2 Features in This Document

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 5

Feature ID Feature Name Section

FBFD-021104 SA Option 2 Architecture 4.1 System Information Broadcast

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 6

SA networking uses the Option 2 architecture. It is an end-to-end 5G network architecture, in

Figure 3-1 SA Option 2 network architecture

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 7

Figure 3-2 Basic signaling process in SA networking

Basic SA networking functions include:

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 8

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 9

4.1 System Information Broadcast

4.1.1 System Information Block Contents

Table 4-1 Contents of the MIB and SIBs

Category Message Content

SIB1 Cell access and selection parameters, and system information

OSI SIB2 Parameters common to different types of cell reselection and

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 10

Category Message Content

SIB3 Intra-frequency neighboring cells and their reselection

SIB5 Inter-RAT frequency list and reselection parameters of each

4.1.2 System Information Scheduling Periods

Figure 4-1 System information delivery path

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 11

Table 4-2 System information scheduling periods

Category Sub- Channel Transmission Scheduling Retransmission

MSI MIB BCCH > Periodic 80 ms It is 20 ms by

SIB1 BCCH > Periodic 160 ms It is 20 ms by

OSI SIB2 BCCH > Periodic 320 ms No

SIB3 BCCH > Periodic 320 ms No