5G Access Problem Analysis

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 Objectives

 Upon completion of this course, you will be able to:

 Master the basic principles of 5G access.
 Master the troubleshooting roadmap for 5G access problems.
 Master the analysis of common 5G access problems.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

 Contents

1. 5G Access Procedure

2. 5G NSA Access Problem Analysis

3. 5G SA Access Problem Analysis

4. Access Problem Case Analysis

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

NSA Networking Mode

 Non-StandAlone (NSA) networking: The existing LTE radio access network and core network
are used as anchor points for mobility management and coverage, and 5G access is added.
For details about the 5G architecture evolution path, see 3GPP TR 38.801.

 The current version supports two scenarios: SCG split horizon (option 3X) and MCG split
horizon (option 3).

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

SA Networking Mode (1)

 The SA Option 2 architecture consists of the 5G

Core Network (GC) and NG Radio Access
Network (NG-RAN). The 5GC architecture
consists of the Access and Mobility Management
Function (AMF) and User Plane Function (UPF).
The NG-RAN architecture consists of the gNodeB
and UE.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

SA Networking Mode (2)

 The interfaces between NEs are as follows:

 The gNodeB is connected to the AMF through the
NG-C interface to implement NG control plane
functions. Connects to the UPF through the NG-U
interface to implement NG user plane functions.
 gNodeBs are connected through the Xn-C and Xn-
U interfaces to implement Xn control plane and
user plane functions, respectively.
 The gNodeB is connected to the UE through the
Uu interface to implement the new radio function.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

NSA Dual Connection Establishment Procedure (Option 3x)
UE eNodeB gNodeB S-GW MME
Option 3x
RRC CONN REQ EPC

RRC CONN SETUP

RRC CONN SETUP CMP LTE NR

UL NAS TRANS
INIT UE MESSAGE
INIT UE CONTEXT SETUP REQ
UE Initial
UE CAP ENQUIRE
Access
UE CAP
Option 3x
UE CAP IND
SEC CMD EPC

SEC CMP
RRC RECFG LTE NR

RRC RECFG CMP

INIT UE CONTEXT SETUP RSP

RRC RECFG(5G Cell Measure by B1 )

5G neigbour RRC RECFG CMP
Measure B1 MEAS RPRT

X2 SetUp Req
Option 3x
X2 Setup Rsp
EPC
SgNB Addition Req
5G SCG ADD
SgNB Addition Rsp
RRC RECFG LTE NR
（5g Scell Add）
RRC RECFG CMP
SgNB RECFG CMP
RANDOM ACCESS Option 3x

Data Forwarding EPC

Path Update Data Forwarding

Procedure ERAB MOD IND LTE NR

Bear Modication
（Opt 3x）
ERAB MOD CNF

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

SA Access Procedure

 After the UE is powered on, it determines the PLMN to be selected based on Power on

the NAS indication.

PLMN search
 The AS performs cell selection and reselection based on the determined PLMN.
 Initial cell selection: The UE scans all RF radio channels based on the NR frequency Frequency scan
band supported by the UE. On each frequency, the UE searches for the strongest cell.
Cell search
 Cell selection based on the stored frequency information: The eNodeB performs cell
selection based on the stored frequency information. If no suitable cell is found, the
eNodeB performs initial cell selection. System messages reading

 After selecting a cell, the UE initiates random access based on the RACH
parameters carried in SIB1. Cell camping

 The UE sets up an RRC connection and initiates a registration procedure to

Register procedure
register with the network.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

UE Initial Registration
UE gNB AMF PCF AUSF UDM

RRC Setup Request

RRC Set up RRC Setup 4
Nausf ：
Initial UE Message Nudm ：
Authentication
Registration Request Authentication get
Request
RRC Connection Setup Complete Request
NAS Authentication Request Nausf ： Authentication Nudm ： Authentication get
Authentication Response Response
Nausf ： Authentication
Authentication Response
Request
Nausf ： Authentication Response
NAS Security Security Mode Command
Security Mode Complete Nudm ： Subscription data get

Nudm ： Subscription data

response
Policy Association Establishment
during Registration

Initial Context Setup Request

UE Cap Enquiry Registration Accept
UE context set up
UE Cap INFO
UE Cap INFO Ind
Security Mode Command

AS Security Security Mode Complete

RRC Reconfiguration
Registration Accept
Registration Registration
Complete Complete

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

 Contents

1. 5G Access Procedure

2. 5G NSA Access Problem Analysis

3. 5G SA Access Problem Analysis

4. Access Problem Case Analysis

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

NSA Access Problem Overview
 Procedure on the LTE Side
 LTE access failure
 No B1 event sent after accessing the LTE network
 B1 event not reporting from UE side

 Procedure on the access preparation

 No SgNB Add Req after receiving B1 event
 SgNB Add Reject from NR
 No SgNB Reconfig Cmp sent from LTE to NR

 Procedure on the NR air interface

 No RA from UE
 RAR time out
 RAR received but MSG3 Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

Common NSA Access Problems (1)

 The UE does not initiate an access request on the LTE side.

 The device-pipe synergy switch is turned off in the LTE cell, and the CPE does not initiate access to
the cell.
 The CPE does not initiate an access request when the LTE cell is in the barred state.

 The UE fails to access the LTE network.

 The CPE version is incorrectly configured.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

Common NSA Access Problems (2)

 The LTE network does not deliver NR measurement control information.

 The NSA switch is turned off on the LTE side.
 The PCC anchoring and Scg configurations are not configured. The PCC frequency must be
consistent with the LTE cell frequency. The Scg frequency is configured as the NR SSB frequency
from RAN2.0 onwards.
 QCI check. The GBR bearer does not support NSA DC (QCI 1-4).
 The 5G neighboring cell configuration on the LTE side is incorrect.
 The EPC sends an S1AP_INITIAL_CONTEXT_SETUP_REQ message containing the "nRestriction" IE to
prohibit the UE from performing NSA services.
 NSA DC cannot be set up for emergency call UEs.
 Check the LTE UE capability reported on the LTE side.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

Common NSA Access Problems (3)

 The UE fails to search for a cell or no B1 measurement report is reported.

 Check whether the NR cell status is normal.
 Check the transmit power of AAU channels.
 When the AAU channel power is less than 14.9 dBm, the AAU transmit power may be abnormal.
 Check whether the NR frequency configured on the LTE side is the NR SSB frequency.
 The cell search fails due to interference from neighboring 5G cells. If downlink interference from
neighboring cells is suspected, use a frequency scanner or the UE spectrum scanning function to
check whether downlink interference exists.
 Whether the UE measurement result meets the B1 threshold

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Common NSA Access Problems (4)

 The eNodeB does not trigger the Add procedure after receiving a measurement report.
 Check whether the X2 interface is normal.
 Check whether the neighbor relationship is correctly configured, whether the neighbor relationship corresponds
to the 5G peer end, and whether PCI conflicts exist.
 Check whether the PLMN configured on the 4G base station is consistent with that configured on the 5G base
station.
 Check whether the local and peer IP addresses of the X2 user plane are configured and whether the peer IP
address can be pinged.

 The NR does not respond to the SgNB Add Req message.

 NSA configuration
 The internal processing of the NR product is delayed, and the message processing duration in each phase can be
viewed in the L3 DBG log.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

Common NSA Access Problems (5)

 The NR responds with an SgNB Add Reject message.

 NSA configuration
 NR user-plane setup failure
 Dedicated preamble allocation failure
 Check whether the NR cell status is abnormal.

 The UE does not initiate an access request over the air interface.
 The UE Does Not Initiate Access Because the PDCP SN Sizes of the LTE and NR Are Inconsistent

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Common NSA Access Problems (6)

 RAR timeout
 In 2.6 GHz networking, the NR frame offset is incorrectly set. As a result, the base station cannot
receive the preamble due to LTE interference. The FFT uplink spectrum scanning result shows that
interference exists.

 PRACH Preamble Detection Failure Due to PRACH Resource Occupation by the PUSCH

 When the base station is close to the UE, the downlink power is oversaturated. As a result, the DCI
cannot be detected.

 Run the LST GNBOPERATOR command to check whether the value of NrNetworkingOption is the
same as that on the live network.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

 Contents

2. 5G NSA Access Problem Analysis

2.1 NR Measurement on the LTE Side

2.2 Access Preparation on the NR Side

2.3 Air Interface Access on the NR Side

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

UEs cannot access the LTE network (1)

 Identification Method
 A UE fails to access the LTE network in either of the following scenarios:
 The UE does not initiate an access request on the LTE network. No UE access message is displayed
in the L3 Message window.
 The EPC rejects the attach request initiated by the UE on the LTE network.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

UEs cannot access the LTE network (2)

 Locating Method
 If a UE does not initiate an access request on the LTE network, the following problems may occur:
 CPEs Do Not Initiate Access Requests on the LTE Network Because the LTE Device-Pipe Synergy Switch Is
Turned Off
 The LTE cell status is incorrectly configured.

 The attach request initiated by the UE on the LTE network is rejected by the CN.
 The attach problem is irrelevant to the wireless network. Contact EPC and UE engineers to locate the
problem.
 For details about LTE access failures, see the troubleshooting measures for LTE access failures on the live
network.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 20

The eNodeB does not deliver the B1 measurement configuration
after the UE accesses the LTE network (1)
 Identification Method
 After an NSA UE accesses the LTE network, the 5G B1 measurement control message delivered normally
contains the 5G measObjectNR-r15 IE in the reconfiguration message after the UE accesses the LTE network.

 The Event List in the Probe signaling of the UE shows whether the LTE network delivers the B1 measurement
control message.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 21

The eNodeB does not deliver the B1 measurement configuration
after the UE accesses the LTE network (2)
 Locating Method
 After a UE accesses the LTE network, the LTE network can deliver 5G B1 measurement
configurations only when the following conditions are met:
 The UE capability report contains the R15 UE capability.
 The core network does not prohibit the NSA capability of the UE.
 The NSA switch and neighboring NR frequencies are correctly configured on the LTE side.
 LTE cells support NSA, but some LTE boards do not support NSA.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 22

The UE does not send the B1 measurement report (1)

 Identification Method
 When an NSA DC UE reports B1 measurement, it sends an MR to the eNodeB.

 In the event list of the Probe signaling of the UE, you can also view the event B1 measurement
report reported by the UE.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 23

The UE does not send the B1 measurement report (2)

 Locating Method
 The possible causes are as follows:
 The frequency delivered in the event B1 measurement control message is incorrect.
 The 5G cell status is abnormal or the AAU transmit power is abnormal. As a result, UEs cannot measure the
5G cell.
 The 5G SSB is severely interfered. As a result, UEs cannot measure the 5G network.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 24

 Contents

2. 5G NSA Access Problem Analysis

2.1 NR Measurement on the LTE Side

2.2 Access Preparation on the NR Side

2.3 Air Interface Access on the NR Side

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 25

The LTE network does not initiate an SgNB_ADD message after
receiving event B1 (1)
 Identification Method
 In the Uu interface tracing result, find the Call Id corresponding to the 5G B1 measurement report. In the X2
interface tracing result, check whether the SgNB_Add_Req message corresponding to the Call Id is available.

 Check the X2 interface for the SgNB_Add_Req message corresponding to the CallId.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 26

The LTE network does not initiate an SgNB_ADD message after
receiving event B1 (2)
 Locating Method
 The possible causes are as follows:
 Abnormal neighboring LTE cell configuration (missing configuration or PCI conflict)
 The X2 link to the target eNodeB is abnormal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 27

The SgNB_ADD message is rejected by the NR (1)

 Identification Method
 The X2 interface tracing result shows that the gNodeB responds with an SgNB_Add_Reject message
after receiving the SgNB_Add_Req message.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 28

The SgNB_ADD message is rejected by the NR (2)
 Locating Method
 The SgNB_Add_Reject message carries the cause value. You can preliminarily determine the possible cause
based on the cause value.
 Transport resource not available: The access request is rejected due to a transmission fault on the 5G side. The possible link
is the X2-U link from the LTE base station where the UE is located to the 5G base station or the S1-U link from the 5G base
station to the core network.
 No radio resource available: The license for the number of UEs in the 5G cell is insufficient, or other 5G resources are
abnormal (for example, no SRS resources are available).
 Which of the following methods can be used to locate transmission faults?
 Turn on the GTP-U static detection switch and check whether an X2-U link alarm to the eNodeB serving the UE or an S1-U
link alarm to the core network is generated on the gNodeB.
 Find the EPGroup corresponding to the X2-U link from the gNodeB to the eNodeB serving the UE and the EPGroup
corresponding to the S1-U link from the gNodeB to the core network. Then, run the DSP EPGroup command to check
whether the EPGroup status is normal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 29

The LTE network does not respond with a reconfiguration complete
message
 Identification Method
 The X2 signaling tracing on the NR side shows that the gNodeB does not receive the SGNB_RECFG_CMP
message after sending the SGNB_ADD_REQ_ACK message. As a result, the timer expires, and the gNodeB
initiates a release procedure.

 Locating Method
 The UE may not respond with a reconfiguration complete message in the following scenarios:
 The UE receives the reconfiguration message but fails to decode the message. As a result, the UE does not
respond with the reconfiguration complete message.
 The eNodeB does not send a reconfiguration complete message.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 30

 Contents

2. 5G NSA Access Problem Analysis

2.1 NR Measurement on the LTE Side

2.2 Access Preparation on the NR Side

2.3 Air Interface Access on the NR Side

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 31

The UE does not initiate random access over the air interface (1)

 Identification Method
 In the Uu interface tracing result, the UE sends an SCG_FAIL_INFO message to the LTE network immediately
after receiving an RRC reconfiguration message containing 5G SCG configurations.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 32

The UE does not initiate random access over the air interface (2)

 In the Probe tracing result of the UE, the reconfiguration failure can be viewed in the Event
List and the possible causes of the reconfiguration failure can be viewed in the Key Event List.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 33

The UE does not initiate random access over the air interface (3)

 Locating Method
 The possible causes are as follows:
 The 5G cell search fails. This is mostly caused by the fact that the accessed cell is not the strongest cell or
the inter-cell interference in the area is severe.
 Parameters in the SCG reconfiguration message fail to be verified on the UE side. In this case, terminal
engineers are advised to locate the fault together.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 34

The RAR message times out during air interface access (1)

 Identification Method
 After receiving the RRC reconfiguration message carrying the 5G SCG configuration, the UE sends
an SCG_RAIL_INFO message to the LTE network at a specified interval (depending on the T304
configuration). The cause value in the message is Scg-Access Failure or scg-Change Failure.

 In the Probe tracing result, the access failure information and RAR timeout information is displayed
in the Event List and Key Event List areas, respectively.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 35

The RAR message times out during air interface access (2)

 Locating Method
 The possible causes are as follows:
 The accessed 5G cell is not the strongest cell or the inter-cell interference in the area is severe.
 The PRACH parameter configuration is incorrect or the physical layer causes the access failure.
 It is advised to check whether the accessed cell is the strongest cell and whether the neighboring cell
interference is severe in the area. Then, check the common configuration problems.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 36

Msg3 access failure over the air interface (1)

 Identification Method
 A period of time (related to the Msg3 waiting timer on the base station side, 2.1s by default) after
the 5G base station sends the SGNB_ADD_REQ_ACK message, the X2 interface tracing result shows
that the 5G base station sends the SGNB_REL_REQUIRED message with the cause value of radio-
connection-with-UE-lost.

 In the Probe tracing result of the UE, abnormal print information is displayed in the Event List area.
In the Key Event List area, print information about repeated Msg3 retransmission is displayed.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 37

Msg3 access failure over the air interface (2)

 Locating Method
 The possible causes of the Msg3 failure are as follows:
 Msg3 demodulation fails due to abnormal uplink TA value or uplink interference.
 Msg3 fails due to incorrect parameter settings on the UE or eNodeB side.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 38

 Q&A

1. In NSA networking, after a UE attaches to the LTE network, the eNodeB delivers a 5G
neighboring cell measurement control message but does not receive the measurement
report of the 5G neighboring cell. What are the possible causes for the eNodeB not
receiving the measurement report?

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 39

 Contents

1. 5G Access Procedure

2. 5G NSA Access Problem Analysis

3. 5G SA Access Problem Analysis

4. Access Problem Case Analysis

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 40

SA Access Problem Overview

 SA access fault analysis locates faults segment by segment based on the signaling
interaction process. SA access faults are classified into the following types:
 The UE does not initiate an access request
 Random access failure
 RRC connection setup failure
 Abnormal NGSig and NAS
 Context setup failure
 PDU Session setup failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 41

Common SA Access Problems (1)

 The UE does not initiate an RRC connection setup request.

 Cell barring
 The UE does not support the current cell frequency band and cell SSB frequency configuration.
 The cell camping conditions are not met.
 The PLMN in the USIM registration information is incorrectly configured.

 Random access failure

 The cell root sequence index does not meet the planning requirements.
 The slot assignment and timeslot structure of the cell are incorrectly configured, causing interference to
surrounding sites.
 Extended Cell Access Radius
 Weak coverage or interference exists.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 42

Common SA Access Problems (2)

 RRC connection setup failure

 Interference and weak coverage causes
 SRS/PUCCH resource application fails.
 Access beyond specifications

 Abnormal NGSig and NAS

 NAS process exception (such as REJ and DETACH)
 The eNodeB or configuration is incorrect.
 The AMF or transmission on the core network is faulty.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 43

Common SA Access Problems (3)

 Context setup failure

 Insufficient air interface resources
 Coverage, interference, and top UEs
 The transmission link is faulty.

 PDU Session setup failure

 Transmission link faults
 Air interface interference and weak coverage exist.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 44

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 45

The UE does not initiate an RRC connection setup request (1)

 Identification Method
 If the eNodeB does not receive the RRCSetupReq message, check whether the UE initiates an RRC connection
setup request.
 The UE does not initiate an RRC connection setup request on the NR side. No UE access message is
displayed in the L3 Message window.

In a normal procedure, the UE initiates

an access request. The RRCSetupRequest
message is displayed in the L3 messages
through the test software.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 46

The UE does not initiate an RRC connection setup request (2)

 Fault Locating
 Check whether the cell is successfully set up.
 Check whether ALM-26203 Board Software Program Error is reported.
 Run the DSP NRDUCELL command to query the cell setup failure cause.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 47

The UE does not initiate an RRC connection setup request (3)

Fault Locating
 Check whether the cell is successfully set up.
 Check whether ALM-26203 Board Software Program Error is reported.
 Run the DSP NRDUCELL command to query the cell setup failure cause.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 48

The UE does not initiate an RRC connection setup request (4)

 Check whether the cell transmit power is normal.

 Check whether the maximum transmit power in NRDUCELLTRP is set to a small value.
 Set the maximum transmit power to check whether the maximum transmit power exceeds the AAU capability. If
the maximum transmit power exceeds the AAU capability, the cell cannot be activated.
 Monitor the AAU output power in real time by using the RRU/RFU output power monitoring function on the
WebLMT.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 49

The UE does not initiate an RRC connection setup request (5)

 Check whether the UE receives SIB1 and whether the PLMN delivered in SIB1 is consistent
with the registration information.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 50

The UE does not initiate an RRC connection setup request (6)

 The cell is in the barred state. As a result, UEs cannot camp on the cell.
 Run the UBL NRDUCELL command to unblock the cell.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 51

The UE does not initiate an RRC connection setup request (7)

 The terminal does not support the network frequency band.

 Run the following command to query the frequency bands supported by the cell:

Frequency bands supported by HUAWEI

Frequency band configured for a cell Mate 30 (5G)

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 52

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 53

Random Access Failure (1)

 Identification Method
 On the UE side, the access failure is a random access failure. Alternatively, check the random access
success rate based on traffic statistics.
 Contention-based random access success rate:

N.RA.Contention.Resolution.Succ/N.RA.Contention.Att
 Non-contention-based random access success rate: N.RA.Dedicated.Msg3/N.RA.Dedicated.Att
 The following table lists the common counters related to random access.
− 1911816542 N.RA.Contention.Att: indicates the number of times the random preamble is received.

− Number of Successful 1911816544 N.RA.Contention.Resolution.Succ Contention Resolutions

− 1911816545 N.RA.Dedicated.Att: number of times the dedicated preamble is received

− Number of times Msg3 is received during 1911816546 N.RA.Dedicated.Msg3 non-contention-based random access

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 54

Random Access Failure (2)

 Standard interface signaling identification:

 Random access failures in Msg1 to Msg3
cannot be directly identified from standard
Msg1
interface signaling.

Msg2

Msg3

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 55

Random Access Failure (3)

 Terminal log identification

 When the UE accesses the network normally, you can view the records of Msg1/2/3/4 in the
EventList of the Probe.

If the UE repeatedly sends Msg1, RAR

timeout occurs.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 56

Random Access Failure (4)

 RAR Timeout

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 57

Random Access Failure (5)

 Contention Resolution Timeout

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 58

Random Access Failure (6)

 Fault Locating
 The possible causes of the random access failure are as follows:
 Random Access Failure Due to Weak Coverage or Interference
− Weak coverage: Check whether weak coverage occurs by monitoring the RSRP of the cell on the UE side or the RSRP
reported in the MR.

− Interference: Check whether interference exists on the network based on the RSRP, SINR, or interference detection on
the NMS.

 Extended Cell Access Radius

− Run the LST NRDUCELL command to query the cell radius. If the UE accesses the cell beyond the cell radius, the
random access fails.

 The PRACH parameter configuration is incorrect or the physical layer causes the access failure.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 59

Random Access Failure (7)

 Basic configuration check

 The root sequence index needs to be planned to prevent downlink interference to the local cell
caused by the RAR message sent by the preamble received by neighboring cells.
 NRDUCELLPRACH: RootSequenceIndex=X

 slot assignment and timeslot structure configuration: The slot assignment and timeslot structure
must be consistent on the entire network. If they are inconsistent, uplink and downlink interference
may occur, which may cause random access exceptions.
 slot assignment parameter: SlotAssignment in the NRDUCell MO
 Slot structure parameter: SlotStructure in NRDUCELL

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 60

Random Access Failure (8)

 Basic configuration check

 MOD NRDUCELL:CellRadius=XX; Cell radius. This parameter affects the NCS parameter used for
generating preamble sequences. If this parameter is set to a small value, UEs at the cell edge or at
a medium distance from the cell center cannot access the network.
 PRACH occupation by PUSCH is disabled.
 NRDUCellRsvdParam:RsvdSwParam4_BIT5=0 indicates that the PUSCH-occupied PRACH function does not
take effect.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 61

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 62

RRC Connection Setup Failure (1)

 The RRC connection setup failure includes the following three cases:
 RRC Reject
 RRC No Reply
 RRC Discard

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 63

RRC Connection Setup Failure (2)

 Fault Locating
 RRC Reject Fault Locating
 For RRC Reject problems, the following scenarios need to be checked:
− Check whether the failure of resource allocation or application for SRS/PUCCH resources
results in the RRC REJ message.

− Check whether the problem is caused by other abnormal procedures on the base station.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 64

RRC Connection Setup Failure (3)

 Procedure for locating RRC packet loss

 The N.RRC.SetupReq.Msg.Disc.FlowCtrl counter is incremented by 1 each time the cell discards an
RRC Setup Request message due to flow control. The gNodeB checks whether flow control is
enabled.
 RRC connection requests are discarded because the number of admitted UEs exceeds the
specifications. For example, the number of admitted UEs exceeds the license limit.

 RRC No Reply Fault Locating

 Common causes: interference and weak coverage

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 65

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 66

The NGSig and NAS are abnormal (1)

 Identification Method
 NG Sig problem:
 After the eNodeB sends an initial UE message, the EPC does not respond to any NAS message, context setup request
message, or context release message. In this scenario, analyze the cause together with the core network.
 After the eNodeB sends an initial UE message, the core network directly sends an NG_RESET message to release the single
UE. As a result, the NGSIG setup fails. In this scenario, analyze the cause together with the core network.
 After the eNodeB receives the MSG5 message, the NG link is blocked or an internal exception occurs. As a result, the
eNodeB does not send the initial UE message to the EPC. In this scenario, the cause needs to be analyzed on the base
station side.

 NAS fault symptom:

 The NAS process is abnormal, and the EPC releases the UE.
 The EPC does not send a UE context setup request, and the eNodeB releases the UE context.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 67

The NGSig and NAS are abnormal (2)

 Fault Locating
 NGSig setup exception:
 No Initial UE Message over the NG Standard Interface on the eNodeB: The eNodeB or configuration is
incorrect.
 Initial UE messages are transmitted over the NG standard interface of the base station. The AMF or
transmission on the core network is faulty.
 For details, see the NGSig fault locating method in the following part.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 68

The NGSig and NAS are abnormal (3)

 NAS process exception:

 Analyze the cause in the downlink and uplink NAS messages before the release on the core network.
For details about the cause, see 3GPP TS 24.501. If the problem is directed to the core network,
analyze the problem on the core network side. If the problem occurs on the UE side, analyze the
problem on the UE side. If the cause value indicates the UE, contact EPC engineers to check whether
the uplink and downlink NAS messages are abnormal.
 The EPC does not send a UE context setup request, and the eNodeB releases the UE context. If no
alarm is reported and the transmission is normal during the period when the problem occurs,
contact EPC engineers to locate the cause.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 69

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 70

Context Setup Failure (1)
 Identification Method
 After the gNodeB receives an INITIAL CONTEXT SETUP REQUEST
message from the AMF, an error occurs during message processing,
resulting in a context setup failure. The corresponding counter is
incremented by 1 based on the failure cause each time the gNodeB
sends an INITIAL CONTEXT SETUP FAILURE message to the AMF.
 If the UE context setup fails due to faults at the radio network layer,
the N.UECntx.FailEst.RNL counter is incremented. For details about
faults at the radio network layer, see 3GPP TS 38.413. The
N.UECntx.FailEst.NoRadioRes counter is incremented each time the
UE context setup fails due to insufficient radio resources.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 71

Context Setup Failure (2)

 Fault Locating
 N.UECntx.FailEst.NoRadioRes: indicates the number of context setup failures due to insufficient radio resources.
Check the air interface resources of the eNodeB.
 If the UE context setup fails due to no response from the N.UECntx.FailEst.UeNoReplyUE, further check the air
interface coverage, interference, or abnormal UEs.
 If the context setup failure is caused by transmission problems, check the transmission link.
 Check whether transmission alarms are reported.
 Check the traffic statistics for congestion, packet loss, retransmission, and special CN transmission parameter configurations.
 If a failure response message is received, analyze the cause with the peer end.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 72

 Contents

3. 5G SA Access Problem Analysis

3.1 The UE does not initiate an RRC connection setup request.

3.2 Random Access Failure

3.3 RRC Setup Failure

3.4 Abnormal NG Sig and NAS

3.5 Context Setup Failure

3.6 PDU Session Setup Failure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 73

PDU Session Setup Failure (1)

 Identification Method NG-RAN node AMF

PDU SESSION RESOURCE SETUP REQUEST

PDU SESSION RESOURCE SETUP RESPONSE

 Check whether the UE sends a PDUSessionEstablishmentRequest message. If the UE does not send a
PDUSessionEstablishmentRequest message, further analysis is required on the UE side.
 Check whether the AMF sends a PDU Session Resource Setup Request message over the NG interface. If no,
contact AMF engineers for further analysis.
 Check whether the QoS is successfully set up over the Uu interface and whether the PDU Session Resource
Setup Response message is sent to the AMF over the NG interface. If the message is not sent, the base station
performs further analysis.
 If the PDU Session Resource Setup Response message contains a cause value, the PDU session setup fails. In this
case, further analysis is required based on the cause value.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 74

PDU Session Setup Failure (2)

 Fault Locating
 Check whether the NG-U link and path are configured.
 The UE does not respond with a reconfiguration complete message, causing a PDU session setup
failure.
 The UE receives the reconfiguration message but fails to decode the message. As a result, the UE does not
respond with the reconfiguration complete message. Generally, this problem is caused by version mismatch.
 Interference and weak coverage

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 75

 Contents

1. 5G Access Procedure

2. 5G NSA Access Problem Analysis

3. 5G SA Access Problem Analysis

4. Access Problem Case Analysis

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 76

Case 1: NR SCCs Cannot Be Added During Inter-eNodeB Handovers
(1)
 Problem description
 During a high-quality route test, the eNodeB does not deliver B1 measurement configurations after
an inter-eNodeB handover. As a result, the NR SCell cannot be added.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 77

Case 1: NR SCCs Cannot Be Added During Inter-eNodeB Handovers
(2)
 Problem Confirmation:
 According to Probe logs and eNodeB data, the problem always occurs when the LTE cell with PCI
103 is handed over to the LTE cell with PCI 468. The Probe shows that the LTE cell is successfully
handed over and the UE sends an RRC reconfiguration complete message to the eNodeB.

LTE handover

RRC reconfiguration complete

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 78

Case 1: NR SCCs Cannot Be Added During Inter-eNodeB Handovers
(3)
 However, the base station does not receive the RRC reconfiguration complete message and
subsequent RRC connection reestablishment message. After the UE is powered on again, it
accesses the 5G network normally.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 79

Case 1: NR SCells Cannot Be Added During Inter-eNodeB Handovers
(4)
 Cause analysis:
 The following figure shows the signaling procedure of inter-eNodeB anchoring in NSA networking.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 80

Case 1: NR SCCs Cannot Be Added During Inter-eNodeB Handovers
(5)
 The MAC/RLC layer of the eNodeB receives the RRC reconfiguration message, but the PDCP integrity check of the
RRC reconfiguration message fails. As a result, the RRC reconfiguration message fails to be received.
Integrity check failed.

Integrity check key

 In the same test route, when the CPE is handed over from PCI 103 to PCI 468, the handover is normal and the NR
network is added normally. However, the UE cannot be handed over. Observe the signaling process. Only the
authentication process is available on the UE, and no encryption (SMC) process is available. The CPE performs both
authentication and encryption. Authentication process Authentication process

Encryption Procedure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 81

Case 1: NR SCells Cannot Be Added During Inter-eNodeB Handovers
(6)
 Check on the core network side: The IMSI number segment of the UE is 460082017000301-
303, and the IMSI number segment of the CPE is 460082017000307-309. In the configuration
provided by the core network to the eNodeB, the UE is set to AUTHONLY, and only
authentication is configured but the encryption process is not configured. The CPE is set to
AUTHProtected, which is used for authentication and encryption.
Number segment 30 Only authentication is required.

Authentication and encryption

CPE Number Segment

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 82

Case 1: NR SCells Cannot Be Added for Inter-eNodeB Handovers (7)

 Key analysis: The following analysis shows the key update process in S1-based handover
scenarios. The key update algorithm on the eNodeB side is the same as that on the UE side.
The detailed process is as follows:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 83

Case 1: NR SCells Cannot Be Added for Inter-eNodeB Handovers (8)
 If no encryption procedure is performed on the core network, the core network does not save each {NH NCC}
update and the value is always the value when the UE initially accesses the network. However, the UE saves and
updates the key. As a result, the key on the UE side is inconsistent with that on the eNodeB side, and the PDCP
integrity protection check fails.
 During an X2-based handover, the value of the NH NCC IE is sent from the source eNodeB to the target eNodeB
through the Handover Request message without passing through the EPC. Therefore, the UE can access the
network without encryption, but the S1-based handover fails.
Solution:
 The root cause of this problem is that the core network configuration performs only authentication and does not
perform encryption. As a result, the keys on the UE and base station sides are inconsistent. As a result, the PDCP
integrity check of the RRC reconfiguration complete message fails, and NR cannot be added.
 Contact CN engineers to modify the authentication and encryption configurations.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 84

Case 2: 5G Cell Access Failure Due to Abnormal Indoor Distribution
System (1)
Problem description:
 At site C in city H, access exceptions occur in new 5G indoor coverage cells. After each access attempt,
RAR timeout occurs, causing access failures.
Cause analysis:
 Analyze the UE access process. When the problem occurs, the RSRP of uplink signals of the UE is only –
140 dBm. Perform tests at different locations. It is found that the UE can access the network and
perform services normally near the device.
 The onsite feedback shows that the indoor distribution system uses 2T2R RRUs. Check the cell data
configuration and no exception is found.
 The UE can access the network in some areas. Therefore, the eNodeB works properly.
 The downlink RSRP measured by the UE reaches about –80 dBm in all areas, indicating that the SSB
signal transmission is normal and the channel is normal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 85

Case 2: 5G Cell Access Failure Due to Abnormal Indoor Distribution
System (2)
 The uplink FFT spectrum analysis result shows that there is no uplink interference signal in
the cell spectrum band.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 86

Case 2: 5G Cell Access Failure Due to Abnormal Indoor Distribution
System (3)
 According to the analysis, the basic isolation problem lies in the indoor distributed antenna
system. The VSWR test is performed to determine the channel problem. The VSWR test is
performed using the default parameter. The VSWR value of the used channel is 1.45, which
is normal.
 If the specified VSWR test frequency is 2520 MHz and the VSWR value is greater than 4.5,
signal transmission at this frequency is abnormal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 87

Case 2: 5G Cell Access Failure Due to Abnormal Indoor Distribution
System (4)
 Indicates whether the VSWR value is still greater than 4 when the specified VSWR test
frequency is 2560 MHz.
 Use the multi-frequency test function to test the entire 100 MHz bandwidth (2515–2615
MHz). The VSWR value is high between 2515 MHz and 2585 MHz. This indicates that the
indoor distribution system is faulty. It is suspected that the filter causes the signal
transmission failure.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 88

Case 2: 5G Cell Access Failure Due to Abnormal Indoor Distribution
System (5)
 According to the VSWR test result, the cell frequency is changed to the 40 MHz (2635 MHz
to 2675 MHz) for verification. The UE can access the network and perform services normally
at the abnormal location. This indicates that the problem is caused by the filter in the indoor
distributed system. As a result, some signals are truncated, affecting the UE access.
 The 65 MHz bandwidth on the left side is affected by the filter. As a result, the uplink signal
is weak. After a UE accesses the network, the uplink signal scheduling starts from the low
frequency. As a result, the uplink signal sent by the UE cannot reach the RRU, causing call
drops.

Solution:
 Reconstruct the indoor distributed antenna system and remove the filter to ensure normal
signal transmission.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 89

Case 3: SA Access Failure After SSB Frequency Modification (1)

Symptom
 In a 4.9 GHz SA site, the center frequency is 723334, the SSB GSCN frequency-domain position is 8784,
and the Mate 20X can access the network. After the SSB GSCN frequency-domain position 8753 is
changed, the UE cannot access the network.

Cause Analysis
 The SSB GSCN frequency-domain position is set to 8784, and the Mate 20X can access the network.
This indicates that the UE access is normal.
 Check the signaling tracing result on the base station side. No information is displayed.
 According to the test logs on the UE side, the UE initiates registration only on the LTE network, but the
registration fails. No access attempt is initiated on the SA network.
 Change the SSB GSCN frequency-domain position to 8784 again. The SA access is normal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 90

Case 3: SA Access Failure After SSB Frequency Modification (2)

 Query the operation logs of the BTS. The query result is consistent with the preceding description.
 After the SSB GSCN frequency-domain position is changed to 8753 at 23:00, the base station does not receive
the RRC connection request.
 After the SSB GSCN frequency-domain position is changed to 8784 at point 1, the UE can access the network
normally.

Frequency Numbe Center SSB center Bandwidth

Bandwidth N M GSCN
Band r of RBs Frequency frequency Range
4.9G 100M 273 723334 1254 - 8753 720384 4800-4900

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 91

Case 3: SA Access Failure After SSB Frequency Modification (3)

 According to 3GPP TS 38.101, the SSB GSCN frequency-domain position range in the n79
frequency band is (8480-8880), and the step size is 16.

Range of GSCN
NR Operating Band SS Block SCS SS Block pattern1
(First – <Step size> – Last)

n38 15 kHz Case A 6431 – <1> – 6544

n39 15 kHz Case A 4706 – <1> – 4795
n40 15 kHz Case A 5756 – <1> – 5995
15 kHz Case A 6246 – <3> – 6717
n41
30 kHz Case C 6252 – <3> – 6714
n77 30 kHz Case C 7711 – <1> – 8329
n78 30 kHz Case C 7711 – <1> – 8051
n79 30 kHz Case C 8480 – <16> – 8880
NOTE 1: SS Block pattern is defined in section 4.1 in TS 38.213 [8]

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 92

Case 3: SA Access Failure After SSB Frequency Modification (4)

 The MS searches for the network according to the GSCN rules during frequency scanning.
However, the GSCN8753-8480=273 is not an integer multiple of the step size 16. As a result,
the MS skips the frequency-domain position of 8753 during frequency scanning and fails to
access the network.

Root Cause
 The GSCN setting does not comply with the protocol.

Solution
 Change the value back to 8480 or configure a new GSCN that is an integral multiple of 16 of
the value of Step size.
 The GSCN compliance check mechanism has been added to the MML command for the base
station.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 93
Case 4: SA Site Access Failure Due to Transmission Exceptions (1)

Problem Description
 In an SA test site, the drive test shows that the UE cannot access the network. Version:
BTS3900 V100R016C00SPC100

Problem Analysis
 Configuration check: Parameter settings are correct.
 Signaling tracing result: After receiving the PDU Session RSRC Setup Req message, the
eNodeB directly sends the core network a PDUSession RSRC Setup Rsp message with the
cause value "transport resource unavailable".

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 94

Case 4: SA Site Access Failure Due to Transmission Exceptions (2)

 According to the traced messages, the G-U interface may be abnormal.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 95

Case 4: SA Site Access Failure Due to Transmission Exceptions (3)

 Alarm check: Check whether gNodeB NG user-plane fault alarms are reported at the time
when the problem occurs.

Root Cause
 Abnormal NG-U Interface Due to Transmission Faults

Solution
 Cooperate with the transmission personnel to rectify the transmission fault. The test result
shows that the fault is rectified and the site can access the network normally.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 96

 Q&A

1. Which of the following may cause an RRC connection setup failure? ()

A. RRC Rej

B. RRC NoReply
C. RRC Discard
D. The UE does not send Msg5.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 97

 Summary

 In this course, we have learned the following contents:

 5G NSA/SA Network Architecture
 5G NSA/SA Access Procedure
 5G NSA/SA Access Failure Cause
 Analysis of 5G NSA/SA Access Failures

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 98

Thank You
www.huawei.com