5G Networking and Signaling (5G RAN5.1 - 02)
5G Networking and Signaling (5G RAN5.1 - 02)
Issue 02
Date 2021-04-30
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.
Website: https://www.huawei.com
Email: support@huawei.com
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
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
6 Parameters.............................................................................................................................. 59
7 Counters.................................................................................................................................. 60
8 Glossary................................................................................................................................... 61
9 Reference Documents...........................................................................................................62
1 Change History
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Editorial Changes
Revised descriptions in this document.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Editorial Changes
Revised descriptions in this document.
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.
3 Overview
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.
● 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.
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.
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.
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:
For details about the basic signaling procedures in NSA networking, see 5 Basic
Signaling Procedures in NSA Networking.
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 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.
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
● 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.
● 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.
● 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.)
System information may change during the running process. When system
information changes, the gNodeB performs the following operations:
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.
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.
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
The gNodeB can schedule UEs based on the first in first out (FIFO) policy and
priority-based policy. The NRDUCellPagingConfig.PagingTransPolicy parameter
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.
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.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.
1. A UE sends an RA preamble.
The UE sends an RA preamble using Msg1. Figure 4-8 shows the RA preamble
transmission procedure.
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.
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.
▪ If the upper layer provides the 5G-S-TMSI, the message contains the
5G-S-TMSI.
– 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.
RRC connection release is triggered by context release. For details about RRC
connection release, see 4.1.5.3 Context Release.
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.
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.
contains the PDU session, security key, handover restriction list, UE radio
capability, and security capability.
Figure 4-15 shows the initial context setup procedure.
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.
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.
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
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.
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.
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.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.
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.
Prerequisite Functions
RAT Function Function Reference Description
Name Switch
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.
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.
5.1 Principles
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.
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.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
results, the gNodeB serving the NR neighboring cell can work as the SgNB. Figure
5-2 shows the NR B1 measurement procedure.
NOTE
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.
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.
● The eNodeB sends an SgNB Modification Request message. Figure 5-6 shows
the DRB release procedure.
● The eNodeB sends an SgNB Release Request message. Figure 5-7 shows the
DRB release procedure.
● The gNodeB sends an SgNB Release Required message. Figure 5-8 shows the
DRB release procedure.
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.
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).
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.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
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
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.
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.
----End
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.
----End
8 Glossary
9 Reference Documents