5g NR Sa Accessibility Optimization Guide 1702558453

5G NR SA Accessibility Optimization Guide
5G NR SA Accessibility
Optimization Guide
R1.0
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. I
LEGAL INFORMATION
Copyright © 2019 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any
reproduction or distribution of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the
contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service
marks, of ZTE CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations
or conditions are disclaimed, including without limitation any implied warranty of merchantability,
fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall
not be liable for damages resulting from the use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or
applications covering the subject matter of this document. Except as expressly provided in any
written license between ZTE CORPORATION and its licensee, the user of this document shall not
acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without
further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire
related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. II
P.R.China
518057
Website: http://support.zte.com.cn
Email: 800@zte.com.cn
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. III
Revision History
Product Version Document Version Serial Number Reason for Revision

NSA base station V2.00.21.00 R1.0 First published
Author
Date Document Version Prepared by Reviewed by Approved by

2019/3/23 R1.0 Gu Jian, and Guo Jia
Intended audience: 5G network optimization engineers
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. IV
TABLE OF CONTENTS
1 Overview ......................................................................................................... 1
2 Random Access .............................................................................................. 3

2.1 Initial Random Access ...................................................................................... 5
2.2 Random Access Triggered by RRC_INACTIVE State Transition ...................... 6
3 RRC Connection Setup .................................................................................. 8
4 UE-Dedicated NG Connection Setup ........................................................... 10
5 NAS Procedure ............................................................................................. 11

5.1 Downlink NAS Direct Transfer ........................................................................ 11
5.2 Uplink NAS Direct Transfer ............................................................................. 11
6 UE Capability Enquiry .................................................................................. 13
7 RRC Connection Reconfiguration ............................................................... 14
8 DRB Setup ..................................................................................................... 15

8.1 DRB Setup Triggered by Initial Context Setup ................................................ 16
8.2 DRB Setup Triggered by PDU Session Setup................................................. 17
9 Signaling of Initial Access on the UE Side.................................................. 18
10 Access Problem Troubleshooting ............................................................... 19

10.1 Random Access ............................................................................................. 19
10.2 RRC Connection Setup .................................................................................. 20
10.3 Initial Direct Transfer and NAS Security .......................................................... 20
10.4 PDU Session Setup and SRB/DRB Setup ...................................................... 21
11 Cases of Access Problems .......................................................................... 22

11.1 Case 1 ............................................................................................................ 22
11.2 Case 2 ............................................................................................................ 24
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. V
FIGURES
Figure 1-1 Initial Access Procedure ...................................................................................... 2

Figure 2-1 Contention-Based Random Access Procedure ................................................... 3
Figure 2-2 Contention-Based-Free Random Access Procedure ........................................... 4
Figure 2-3 Initial Random Access Procedure ....................................................................... 5
Figure 2-4 Random Access Triggered by a Transition From RRC_INACTIVE State to
Another State.......................................................................................................................... 7
Figure 4-1 UE-Dedicated NG Connection Setup ................................................................ 10
Figure 5-1 DL NAS Transfer ............................................................................................... 11
Figure 5-2 UL NAS Transfer ............................................................................................... 11
Figure 6-1 UE Capability Transfer ...................................................................................... 13
Figure 7-1 RRC reconfiguration, successful ....................................................................... 14
Figure 8-1 QoS Architecture ............................................................................................... 15
Figure 8-2 UE Context Setup Procedure ............................................................................ 16
Figure 8-3 DRB Setup Triggered by PDU Session Setup ................................................... 17
Figure 9-1 Initial Access Signaling on the UE Side ............................................................. 18
TABLES
Table 2-1 Scenarios for Random Access ............................................................................. 5

Table 3-1 RRC Connection Establishment, Successful ........................................................ 8
Table 3-2 RRC Connection Establishment, Network Reject ................................................. 8
Table 3-3 Parameter Related to RRC Connection Setup...................................................... 9
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. VI
Confidential▲
1 Overview
In the 5G SA networking mode, the NR access includes the following procedures:
1. Random access: When a UE needs to establish a connection with the network for
some reasons (such as service request, location update, and paging), the UE
performs random access first.
2. RRC connection setup: SRB1 is established for transmitting signaling. The UE enters
the RRC_Connected state after successful establishment. This procedure is a part
of RRC connection management for signaling connection management.
3. UE-dedicated NG connection setup: When an initial UE message is sent to the AMF,
the AMF may trigger a downlink NAS message, an initial context request message
or a context release message. The first UE-level NG-interface message received by
the gNodeB indicates that the UE-specific NG connection has been successfully set
up.
4. NAS: When an initial UE message is sent to the AMF, the AMF selectively performs
some NAS procedures (such as identity authentication and NAS security) according
to the contents carried in the NAS message of the UE. For this part, the base station
only passes through the messages as a channel.
5. Initial context setup: This procedure involves many contents, for example, UE
capability enquiry, security activation, and RRC reconfiguration. This procedure
includes signaling connection management (for example, SRB2 establishment and
UE capability enquiry) and service connection management (for example, PDU
Session setup and DRB setup). Successful establishment of the service bearer
indicates that a NG-U tunnel has been successfully established between two UPFs.
ZTE Confidential & Proprietary. © 2019 ZTE CORPORATION. All rights reserved. 1
Confidential▲
Figure 1-1 Initial Access Procedure
Confidential▲
2 Random Access
Random Access Procedure: The UE sends a random access preamble and attempts to
access the network until a basic signaling connection is established between the UE and
the network. Random access is a very important step in the NR system. A UE establishes
a communication link with the base station through the random access procedure.
1. The UE establishes a connection to the base station through the random access
procedure and achieves uplink synchronization.
2. The UE exchanges information with the base station through the random access
procedure to complete subsequent operations, such as system information
application, resource request, and data transmission.
The random access procedure supports two different modes:
1. Contention-based.
2. Contention-based-free.
In the NR system, there are 64 available preamble sequences in each cell. In a contention-
based random access procedure, a UE randomly selects one preamble sequence to
initiate a random access procedure toward the network side. Therefore, if multiple UEs
use the same preamble sequence to initiate a random access procedure at the same time,
a conflict occurs, which may cause access failure. The contention-based-free random
access uses the preamble sequence allocated by the base station to initiate the random
access procedure, so that the conflict between preamble sequences of different UEs can
be avoided.
Figure 2-1 Contention-Based Random Access Procedure
Confidential▲
⚫ Step1: The UE sends a Random Access Preamble message to the gNodeB through
the PRACH.
⚫ Step2: The gNodeB sends a Random Access Response message to the UE in the
RAR time window.
⚫ Step3: The UE sends an MSG3 on the UL-SCH channel.
⚫ Step4: The gNodeB sends a Contention Resolution message to UE on the DL-SCH

channel.
Figure 2-2 Contention-Based-Free Random Access Procedure
⚫ Step0: The gNodeB allocates a dedicated preamble to the UE.
⚫ Step1: The UE sends a dedicated random access preamble to the gNodeB on the
PRACH channel.
⚫ Step2: The gNodeB sends a Random Access Response message to the UE in the
RAR time window RachConfigGeneric.raResponseWindow.
The following table lists the scenarios that may trigger a random access procedure.
Confidential▲
Table 2-1 Scenarios for Random Access
Contention
No. Scenario Triggering Mode
Mechanism
During the initial access, the UE

Upper-layer network Contention-
1 establishes a radio connection with
elements Based
the network.
RRC_INACTIVE turns into Upper-layer network Contention-

2
connected state. elements Based
An SA handover is to be Upper-layer network Contention-

3
performed. elements Based-Free
2.1 Initial Random Access

The UE switches from the RRC_IDLE state to the RRC_CONNECTED state through initial
random access. This process is contention-based. In this scenario, there is no RRC
signaling connection between the network side and the UE, and the UE can only obtain
RACH and PRACH configuration from the SIB. Because the RACH/PRACH configuration
in the SIB is shared by the users in a cell, only the contention-based mode can be adopted.
Figure 2-3 Initial Random Access Procedure
Confidential▲
Procedure:
1. When the UE is powered on, it will detect the SSB of the optimum beam during the
cell search and synchronization process, parse the MIB to obtain the SSB index,
select the PRACH resources according to the PRACH configuration parameters
contained in the SIB message and send a random access preamble.
2. After detecting an MSG1, the base station sends a random access response within
ra-ResponseWindow. The MSG2 PDU contains the preamble index, Timing advance
command, Temporary C-RNTI, and UL grant information.
3. The UE sends an MSG3, that is, RRCConnectionRequest. The MSG3 carries an

important information: Unique ID of each UE — contention resolution ID (generated
from 5G-S-TMSI or 39-bit random number), which is used for MSG4 conflict
resolution.
4. The base station sends an MSG4, that is, RRCConnectionSetup. In the conflict
resolution mechanism, the base station will carry the unique contention resolution ID
of the UE in the MSG4. If the UE receives the contention resolution ID matching the
MSG3, the contention resolution is successful.
5. The UE sends an RRCConnectionSetupComplete message to notify the base station

that the contention resolution is completed and that the air-interface connection is
established.
2.2 Random Access Triggered by RRC_INACTIVE

State Transition
The UE in the RRC_INACTIVE state switches to the RRC_CONNECTED state through
random access. The following scenarios may trigger this kind of random access:
1. Upon receiving the downlink data service from the core network (NAS), the base
station triggers the RAN paging process to wake up the UE. After the UE is woken
up by the RAN Paging, it triggers the Resume process to restore the air-interface
connection of the RRC, and the service can be performed normally.
2. If the UE needs to send uplink services, it triggers the Resume process to resume
the air-interface connection of RRC, and the service can be performed normally.
The random access procedure triggered by a transition from RRC_INACTIVE state to

another state is based on contention.
Confidential▲
Figure 2-4 Random Access Triggered by a Transition From RRC_INACTIVE State to

Another State
Procedure description:
1. Refer to Step 1 in Section 2.1, “Initial Random Access.”
2. Refer to Step 2 in Section 2.1, “Initial Random Access.”
3. The UE sends an MSG3, that is, RRCConnectionActivationRequest. The MSG3

carries important information: Unique ID of each UE — contention resolution ID
(generated from 5G-S-TMSI or 39-bit random number), which is to be used for MSG4
conflict resolution.
4. The base station sends an MSG4, that is, RRCConnectionActivation. In the conflict
resolution mechanism, the base station will carry the unique contention resolution ID
of the UE in the MSG4. If the UE receives the contention resolution ID matching the
MSG3, the contention resolution is successful. The difference from initial access is
that this message is sent on the DCCH.
5. The UE sends an RRCConnectionActivationComplete message to notify the base

station that the contention resolution is completed and that the air-interface
connection is established.
Confidential▲
3 RRC Connection Setup

RRC connection establishment is the procedure of establishing SRB1. Before a dedicated
NG connection is set up, the gNodeB cannot obtain the UE context information from the
AMF. Therefore, it is unnecessary to activate the security mode during the RRC
connection setup, and SRB1 does not enable encryption or integrity protection.
Table 3-1 RRC Connection Establishment, Successful
Table 3-2 RRC Connection Establishment, Network Reject
1. The UE triggers the RRC connection setup procedure by sending the gNodeB an
RRCSetupRequest message, and starts the waiting timer UeTimer.t300 (the duration
of the T300 timer is sent in the SIB1 through the broadcast message). Upon receiving
this message, the gNodeB performs UE resource admission.
2. If the resource admission is successful, the gNodeB sends the UE an RRCSetup

message, asking the UE to configure SRB1 and set up an RRC connection. At the
same time, the gNodeB configures the local resources and the UE kills the T300
timer. If the resource admission fails, the gNB sends an RRCReject message to the
UE, refusing to set up an RRC connection. If the UE does not receive the RRCSetup
message, the T300 timer will expire and the process will end in failure.
3. After the UE completes the SRB1 configuration, it replies to the gNB with an
RRCSetupComplete message, which indicates that the RRC connection setup
procedure is completed successfully.
Confidential▲
Table 3-3 Parameter Related to RRC Connection Setup
Parameter UeTimer.t300
Short
T300
Name
This parameter specifies the timer length for the UE to wait for the
RRC connection response. When the UE sends an RRC connection
request message, the T300 timer will be started. Before the timer
expires, if any of the following events occurs, the timer will stop.
1. The UE receives an RRCConnectionSetup or
RRCConnectionReject message.
2. The cell-reselection procedure is triggered.
Description
3. The NAS layer terminates the RRC connection setup procedure.
If the timer expires, the UE will trigger the following operations:
1. Reset the MAC layer.
2. Release the MAC layer configuration.
3. Reset all the RLC entities that have established radio bears (RBs)
and notify the upper-layer network elements of the RRC connection
setup failure.
Value
100, 200, 300, 400, 600, 1000, 1500, 2000
Range
Default
600
Value
Confidential▲
4 UE-Dedicated NG Connection Setup

The following figure shows the procedure of UE-dedicated NG connection setup.
Figure 4-1 UE-Dedicated NG Connection Setup
1. The gNodeB sends an InitialUEMessage message to the AMF, carrying the RAN UE
NGAP ID allocated by the gNodeB, NAS PDU, location information and access
reason.
2. Upon receiving the InitialUEMessage message, the AMF decides a series of optional
NAS processes (such as identity authentication and NAS security) according to the
carried information. And it determines whether to initiate or release a context
according to the service request of the UE. Therefore, the first downlink NG-interface
message sent by the AMF may be a DOWNLINK NAS TRANSPORT,
InitialContextSetupRequest or UE CONTEXT RELEASE COMMAND message,
which may carry the AMF UE NGAP ID allocated by the AMF. When the gNodeB
and the AMF respectively have a unique identifier, it is deemed that the UE-dedicated
NG connection (signaling connection) is set up successfully, and the gNodeB can
communicate with the AMF normally.
Confidential▲
5 NAS Procedure
5.1 Downlink NAS Direct Transfer
Figure 5-1 DL NAS Transfer
Procedure of downlink NAS direct transfer:
1. The AMF sends the downlink NAS PDU to the gNodeB through the DOWNLINK NAS
TRANSPORT message.
2. The gNodeB forwards the downlink NAS PDU to the UE through the
DLInformationTransfer message.
5.2 Uplink NAS Direct Transfer
Figure 5-2 UL NAS Transfer
Procedure of uplink NAS direct transfer:
1. The UE sends the uplink NAS PDU to the gNodeB through the
ULInformationTransfer message.
Confidential▲
2. The gNodeB forwards the uplink NAS PDU to the AMF through the UPLINK NAS
TRANSPORT message.
Confidential▲
6 UE Capability Enquiry
Some functions and parameter configurations of the gNodeB are limited by the UE
capability, so the UE capability enquiry procedure is necessary. The gNodeB saves the
UE capability enquiry result as a basis for decision making and sends it to the AMF for
storage.
UE capability enquiry can be implemented in the following two cases:
1. Upon receiving the RRCSetupComplete message from the gNodeB, the RRC
connection setup is completed and the enquiry is initiated.
2. Upon receiving the INITIAL CONTEXT SETUP REQUEST message sent by the
AMF, the gNodeB judges whether to initiate the UE capability enquiry procedure. If
the INITIAL CONTEXT SETUP REQUEST message carries the UE capability
information, the enquiry is not initiated. Otherwise, the enquiry is initiated.
The protocol only describes Case 2, but the gNodeB can optimize the implementation
selectively. If the optimization switch GlobalSwitchInformation.ueCapOptimizeSwitch is
turned on, select Mode 1, which happens at the same time with the sending of the initial
UE message to the AMF, so as to accelerate the whole access procedure.
Figure 6-1 UE Capability Transfer
For the UE capability enquiry procedure, see the following figure.
1. The gNodeB sends a UECapabilityEnquiry message to the UE, carrying a list of the
radio access type to be queried, such as nr, eutra-nr, and eutra.
2. The UE replies to the gNodeB with a UECapabilityInformation message to provide

the UE radio capability as required by the gNodeB.
3. The gNodeB sends a UE RADIO CAPABILITY INFO INDICATION message to the

AMF.
Confidential▲
7 RRC Connection Reconfiguration

Figure 7-1 RRC reconfiguration, successful
When the RRC connection between the gNB and the UE has been set up, if the gNB
needs to reconfigure the RRC connection due to the addition/deletion of SRB2, DRB,
measurement, or a secondary cell, or other configuration changes, it will send an
RRCReconfiguration message to the UE, instructing the UE to use the new RRC
connection configuration. In addition, this message may carry UE-dedicated NAS
information.
Confidential▲
8 DRB Setup
For service bearers in a 5G network, NGU tunnels and DRBs do not correspond to each
other in a one-to-one way. The concept of PDU session has been introduced. One UE
may have multiple PDU sessions at the same time. One PDU session corresponds to
multiple DRBs, but one DRB does not correspond to multiple DRBs. Each PDU session
has a default DRB. The following figure shows the relationship between the PDU session,
QoS flow and DRB.
Figure 8-1 QoS Architecture
Confidential▲
8.1 DRB Setup Triggered by Initial Context Setup
Figure 8-2 UE Context Setup Procedure
Initial context setup procedure:
1. The AMF sends an INITIAL CONTEXT SETUP REQUEST message to trigger the
UE context setup process, carrying the information such as the security, UE radio
capability (optional), and PDU Session Setup List (optional).
2. Upon receiving the INITIAL CONTEXT SETUP REQUEST message, the gNodeB
performs the SRB2 setup, security activation, UE capability enquiry (optional) and
PDU session setup (optional) procedures. Security activation and UE capability
enquiry are described separately. This section focuses on the SRB2 and DRB setup
after security activation. After security activation, signaling transmission on SRB1 is
encrypted and protected for integrity. For SRB2 setup, the local and air interfaces
can be configured if resource admission is successful. For DRB setup, the mapping
between the QoS Flow and the DRB should be performed first. Only when the
mapping and resource admission are successful and a downlink GTPU tunnel at the
level of PDU session is established, can the local and air interfaces be configured.
Air interface configuration is performed through the RRCReconfiguration message,
which carries a list of the SRBs and DRBs to be set up and the related resources. If
the initial context is successfully set up, the gNodeB will reply to the AMF with an
INITIAL CONTEXT SETUP RESPONSE message, which may carry a list of the failed
PDU sessions. Otherwise, the gNodeB will send an INITIAL CONTEXT SETUP
FAILURE message.
Confidential▲
8.2 DRB Setup Triggered by PDU Session Setup
Figure 8-3 DRB Setup Triggered by PDU Session Setup
DRB setup triggered by PDU SESSION RESOURCE SETUP REQUEST:
1. The gNodeB receives the PDU SESSION RESOURCE SETUP REQUEST message
from the AMF. This message carries a list of the PDU sessions to be set up, and
each PDU session contains a list of the QoS flows to be set up. The gNodeB first
needs to perform mapping between the QoS flow and DRB (here, DRB setup). After
the mapping and resource admission are successful and a downlink GTPU tunnel at
the level of PDU session is established, the local and air interfaces can be configured.
2. The gNodeB sends an RRCReconfiguration message to the UE, carrying the

information of a list of the DRBs to be set up. The UE configures the resources at
each layer of the DRB.
3. When the UE completes the configuration successfully, and it sends an

RRCReconfigurationComplete message to gNodeB.
4. The gNodeB sends a PDU SESSION RESOURCE SETUP RESPONSE message to

the AMF, which contains a list of the successfully established PDU sessions and a
list of the failed PDU sessions. The list of successful PDU sessions contains a list of
successful and failed QoS flows, and downlink GTPU information should be carried
for each successfully established PDU session.
Confidential▲
9 Signaling of Initial Access on the UE

Side
Figure 9-1 Initial Access Signaling on the UE Side
Initial access signaling seen from the UE side:
1. Signaling 620-626: RRC connection setup, including the random access procedure.
2. Signaling 627-639: including uplink/downlink NAS direct transfer, authentication,

encryption and registration completion.
3. Signaling 640-642: PDU session setup.
4. Signaling 643-646: SRB and DRB setup.
Confidential▲
10 Access Problem Troubleshooting

1. Check the cell status first.
− Check whether each board and the AAU are in a normal state and whether the
cell is working.
− Check whether the cell has any alarm and analyze the alarm. If there is an alarm,
notify ZTE product support engineers to handle it.
2. When the cell is in a normal state, analyze the access problem. The UE’s access
procedure can be divided into four phases:
i. Random access.
ii. RRC connection setup.
iii. Initial direct transfer and NAS security.
iv. PDU session setup and SRB/DRB setup.
The analysis is performed phase by phase and the process is similar to that of LTE.
10.1 Random Access

Judging from the past experience, the probability of problems occurring in the random
access phase is relatively small. If one of the following situations exists, the random
access may be faulty.
1. Check the OSS KPI statistics: if the number of times that the random access
preamble of GroupA or GroupB is successfully detected in the cell is 0, there must
be some problem with the cell in the random access phase.
2. Check the background statistics: if many MSG1 and MSG2 are successfully detected
but meanwhile many MSG3 and MSG4 are not detected successfully (or the number
of successfully detected MSG3 and MSG4 is nearly zero), there must be some
problem with the cell in the random access phase.
3. Analyze the foreground test results: in the RRC access phase, if only a large number
of RRCconnectionRequest messages are seen but there are no subsequent access
messages, there must be some problem with the cell in the random access phase.
To locate a random access problem, the following measures can be taken:
1. Analyze and check whether the PRACH logical root sequence is reused.
2. Analyze whether it is possible that the Ncs value is set too small.
Confidential▲
3. Analyze whether the MSG1 false detection suppression threshold is not sufficiently
set.
4. Check whether the optical module configuration and the optical fiber distance meet
the engineering requirements.
5. Analyze whether there is uplink interference.
6. If no problem is found through the above-mentioned analysis, contact the technical

support department or report the problem to the first response group.
10.2 RRC Connection Setup

This procedure starts from the reception of the RRC Connection Request message by the
base station. If there are many RRC connection setup failures, the following procedure
should be followed for troubleshooting:
1. If the base station sends an RRC rejection message rather than an RRC Connection
Setup message, it is likely that there is some problem at the base station side. The
possible causes include that:
i. RRC admission threshold parameters are not properly configured.
ii. The CPU usage of the base station has an over-high upper limit.
2. The base station sends an RRC Connection Setup message but does not receive an
RRC Connection Complete message. The possible causes include that:
i. The uplink interference of the cell is high.
ii. The downlink coverage is poor.
iii. The cell capacity level indication is set to an over-small value, or the SR channel
capacity is too small.
iv. The reselection parameters for the camp state are not reasonable, and the UE
fails to reselect a proper serving cell in time.
If no problem is found through the above-mentioned analysis, contact the technical

10.3 Initial Direct Transfer and NAS Security

If there is any problem with initial direct transfer or NAS security, contact core network
engineers for assistance.
Confidential▲
10.4 PDU Session Setup and SRB/DRB Setup

The following procedure can be followed to troubleshoot PDU session setup and
SRB/DRB setup step by step:
1. Upon receiving the Initial Context Setup Request message, if the eNB directly replies
with a setup failure message, the possible causes include that:
i. The ERAB admission fails, probably due to the ERAB admission threshold or
insufficient licenses.
ii. The UE capability carried by the AMF conflicts with that at the RAN side, for
example, the UE initiates access in a cell, but the UE capability sent from the
MME indicates that the UE does not support the frequency band.
iii. The UE capability information is too long and exceeds the upper limit of the
base station version.
2. If the SRB/DRB setup fails during the encryption and integrity protection on the air
interface, it is necessary to check the encryption and integrity protection algorithms
set at the base station side and set them according to the technical notice.
3. Another common case is that during the SRB/DRB setup, the base station performs
RRC reconfiguration for the UE, but the reconfiguration fails, resulting in an
SRB/DRB setup failure. The possible causes include:
i. The UE capability is insufficient.
ii. There is some problem with the system version of the base station.
iii. There is some problem with the physical configuration of the base station.
4. In addition, in the phase of PDU session setup and SRB/DRB setup, the air-interface
quality should be guaranteed, because if the air-interface link quality is very poor, the
access should have failed in the phase of RRC connection setup. However,
occasionally the messages on the air interface may have no response, so the
following actions should be taken:
i. Check the uplink interference of the cell.
ii. Check the downlink coverage.
iii. Check whether the cell capacity level indication is set to an over-small value, or
whether the SR channel capacity is too small.
If no problem is found through the above-mentioned analysis, contact the technical

Confidential▲
11 Cases of Access Problems
11.1 Case 1
Problem Description
PING service failed after an SA version upgraded.
After the SA equipment in the SA area was upgraded to V2.00.20.01P08, the access was
successful, but the PING service kept failing due to request timeout, and the problem
persisted after the CPE was restarted.
Problem Analysis
ZTE colleagues at the core network side traced the signaling and found that the core
network responded to the uplink PING packet and sent the response to the base station,
but the CPE side did not received it. ZTE colleagues at the base station side traced the
signaling and found that the CU side received the response from the core network and set
it to the DU side. It was suspected that the CPE failed to identify the MAC address of the
testing laptop.
Optimization Solution
The engineers bound the MAC address of the testing laptop with the CPE: Telnet to
192.254.1.16, pad to the Product process, and type in SetPcMAC 0x68,0x
F7,0x28,0x85,0xDB,0x3B.
E0-B9-4D-B1-BC-91 was the MAC address of the PC network card directly connected to
the CPE-Debug port. Please note that 0x is the number 0 and the lower case letter x.
Confidential▲
The command for querying the MAC address in the process is PcMAC.
Optimization Effect
The engineers bound the MAC address of the testing laptop with the CPE, and restarted
the CPE after powering it off. Then the PING service became normal. This error appeared
occasionally, and it was unnecessary to bind the MAC address for every test.
Confidential▲
11.2 Case 2
Problem Description
The CSI measurement information was null after an SA version upgraded.
After the SA equipment in the SA area was upgraded to V2.00.20.01P08, the CSI
information displayed on the KPI tab under Statistics on the LMT was null.
Problem Analysis
Because the UE could access the cell properly and SSB-related information could be
displayed properly, it was preliminarily concluded that CSI-related measurement was
disabled.
Confidential▲
Optimization Solution
The engineers checked the background parameter configuration and found that the
csiRsEnable parameter value was set to false.
Optimization Effect
The engineers changed the csiRsEnable parameter value from false to true, and then
the CSI information could be displayed normally.

5g NR Sa Accessibility Optimization Guide 1702558453

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5g NR Sa Accessibility Optimization Guide 1702558453

Uploaded by

Copyright:

Available Formats

5G NR SA Accessibility Optimization Guide

Copyright © 2019 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Hi-tech Road South

Product Version Document Version Serial Number Reason for Revision

Date Document Version Prepared by Reviewed by Approved by

Intended audience: 5G network optimization engineers

2 Random Access .............................................................................................. 3

3 RRC Connection Setup .................................................................................. 8

4 UE-Dedicated NG Connection Setup ........................................................... 10

5 NAS Procedure ............................................................................................. 11

6 UE Capability Enquiry .................................................................................. 13

7 RRC Connection Reconfiguration ............................................................... 14

8 DRB Setup ..................................................................................................... 15

9 Signaling of Initial Access on the UE Side.................................................. 18

10 Access Problem Troubleshooting ............................................................... 19

11 Cases of Access Problems .......................................................................... 22

Figure 1-1 Initial Access Procedure ...................................................................................... 2

Table 2-1 Scenarios for Random Access ............................................................................. 5

Figure 1-1 Initial Access Procedure

The random access procedure supports two different modes:

Figure 2-1 Contention-Based Random Access Procedure

⚫ Step3: The UE sends an MSG3 on the UL-SCH channel.

⚫ Step4: The gNodeB sends a Contention Resolution message to UE on the DL-SCH

Figure 2-2 Contention-Based-Free Random Access Procedure

⚫ Step0: The gNodeB allocates a dedicated preamble to the UE.

Table 2-1 Scenarios for Random Access

During the initial access, the UE

RRC_INACTIVE turns into Upper-layer network Contention-

An SA handover is to be Upper-layer network Contention-

2.1 Initial Random Access

Figure 2-3 Initial Random Access Procedure

3. The UE sends an MSG3, that is, RRCConnectionRequest. The MSG3 carries an

5. The UE sends an RRCConnectionSetupComplete message to notify the base station

2.2 Random Access Triggered by RRC_INACTIVE

The random access procedure triggered by a transition from RRC_INACTIVE state to

Figure 2-4 Random Access Triggered by a Transition From RRC_INACTIVE State to

1. Refer to Step 1 in Section 2.1, “Initial Random Access.”

2. Refer to Step 2 in Section 2.1, “Initial Random Access.”

3. The UE sends an MSG3, that is, RRCConnectionActivationRequest. The MSG3

5. The UE sends an RRCConnectionActivationComplete message to notify the base

3 RRC Connection Setup

Table 3-1 RRC Connection Establishment, Successful

Table 3-2 RRC Connection Establishment, Network Reject

2. If the resource admission is successful, the gNodeB sends the UE an RRCSetup

Table 3-3 Parameter Related to RRC Connection Setup

4 UE-Dedicated NG Connection Setup

Figure 4-1 UE-Dedicated NG Connection Setup

5.1 Downlink NAS Direct Transfer

Figure 5-1 DL NAS Transfer

Procedure of downlink NAS direct transfer:

5.2 Uplink NAS Direct Transfer

Figure 5-2 UL NAS Transfer

Procedure of uplink NAS direct transfer:

UE capability enquiry can be implemented in the following two cases:

Figure 6-1 UE Capability Transfer

For the UE capability enquiry procedure, see the following figure.

2. The UE replies to the gNodeB with a UECapabilityInformation message to provide

3. The gNodeB sends a UE RADIO CAPABILITY INFO INDICATION message to the

7 RRC Connection Reconfiguration

Figure 8-1 QoS Architecture

8.1 DRB Setup Triggered by Initial Context Setup

Figure 8-2 UE Context Setup Procedure