5G NSA Call Drop Failures Possible Causes Troubleshooting Methods 1
5G NSA Call Drop Failures Possible Causes Troubleshooting Methods 1
5G NSA Drop
Analysis Guide
Or it might include others cause such as "Handover Desirable for Radio Reasons", "Load Balancing“, etc.
3GPP TS 37.340 version 15.5.0 Release 15 (Page 34 onwards) *All 3GPP Release causes will be added to the video description
3GPP TS 38.423 version 16.2.0 Release 16 (Page 221 to 223)
SN Release procedure(Abnormal Release)
• The detection of NR Radio Link Failure (RLF) can be carried out by either the UE(MN) or the gNodeB (SN).
• A 5G Call Drop (RLF) is identified and declared through various factors, including transmission issues, core
problems, 5G Downlink (DL) and Uplink (UL) radio frequency (RF) issues, UE capability issues, 4G RF issues
(RRC Reestablishment), and lastly, configuration issues.
SN Release procedure - SN initiated When the signal quality of the Primary Serving Cell (PSCell) consistently diminishes, and
there is no suitable neighboring cell identified for a PSCell handover, the decision to
delete the PSCell can be triggered by event A2
eNode gNode
UE B B S-GW MME
MN SN
MR RRC Transfer
1.SgNB Release
Required
2.SgNB Release
Confirm
gNodeB Cell
3.RRC
SN
Reconfiguration
4.RRC Reconfig
CMP
eNodeB Cell
5. SN Status
Transfer MN
6. Data
Forwarding
A2 Threshold
7. Secondary RAT for SN Removal
Data Volume Report
eNodeB gNodeB
UE S-GW MME
MN SN
1.SgNB Release
Non-Anchor
Request
2.SgNB Release
Request Ack
3.RRC Reconfiguration
6. Data Forwarding
7. Secondary RAT
Data Volume Report
eNodeB gNodeB
UE S-GW MME
MN SN
1.SgNB Release
Required
2.SgNB Release
Confirm
3.RRC Reconfiguration
4.RRC Reconfig CMP
5. SN Status Transfer
6. Data Forwarding
7. Secondary RAT
Data Volume Report
UE
eNodeB
MN
gNodeB
SN
S-GW MME The SgNB release due to inactivity timer can be triggered
1.SgNB Release
Request
by MN or SN based on the network parameters when the
2.SgNB Release
Request Ack SgNb is in the inactive state
3.RRC Reconfiguration
6. Data Forwarding
7. Secondary RAT
Data Volume Report
eNodeB gNodeB
3GPP TS 38.423 definition
UE
MN SN
S-GW MME
Radio Network
Meaning
1.SgNB Release
Required
Layer cause
2.SgNB Release
Confirm
3.RRC Reconfiguration The action is requested due to user inactivity on all PDU Sessions. The action may be
4.RRC Reconfig CMP performed on several levels:
5. SN Status Transfer • on UE Context level, if NG is requested to be released in order to optimize the radio
User Inactivity resources; or S-NG-RAN node didn't see activity on the PDU session recently.
6. Data Forwarding • on PDU Session Resource or DRB or QoS flow level, e.g. if Activity Notification
7. Secondary RAT
Data Volume Report indicate lack of activity
8. Path Updte Procedure In the current version of this specification applicable for Dual Connectivity only.
9.UE Context Release
Master
Node • A 5G Call Drop (RLF) is identified and declared through
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues
various factors, including and not limited to the following:
2. Core problems
Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary
Node
Retainability Issues
3. Transmission issues
UE is in the uplink UL related timers
out-of-synchronization state
Coverage, BLER, DL
Secondary 4. 5G Downlink (DL) and Uplink (UL) radio
Maximum number of DL RLC Node
Radio Condition PDCCH
retransmissions in is reached
Feature check
5. frequency (RF) issues
UL Interference
RACH Configuration
RA Problems during
Access or Handovers
Cell Radius
No Dominanet Cell
6. UE capability issues
5G during HO
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues
UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues eNode gNode
UE S-GW MME
B B
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues
UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues UE eNodeB gNodeB
DL Packets
Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary
Node DL Packets DL Data
Retainability Issues DL Packets Transfer
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues
UE eNodeB gNodeB
Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues UE eNodeB gNodeB
UL Packets
UE is in the uplink UL related timers UL Data
Transfer UL Packets
out-of-synchronization state
Secondary
Coverage, BLER, DL
Maximum number of DL RLC Node
Radio Condition PDCCH UL Packets
retransmissions in is reached
Feature check
SCG Failure
UL Interference Information
RACH Configuration SgNB Release Request
RA Problems during 5G Drop due
Cell Radius to MAXULTX
Access or Handovers No Dominanet Cell 2.SgNB Release Request
Ack
5G during HO
UE eNodeB gNodeB
DL Packets
UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO
MN(UE)
5G Non-Standalone Drops Breakdown per MN & SN
Master Node
SN
Radio
DL MAX RLC
UE Lost UL SYN
RACH
Cell Radius A2 RSRP for SgNB Release
Format
preambleReceivedTarget
Power powerRampingStep B1 Threshold for SgNB A5 Threshold for PScell
Addition Change
preambleTransMax