100% found this document useful (1 vote)
143 views17 pages

5G NSA Call Drop Failures Possible Causes Troubleshooting Methods 1

5g drop call issues

Uploaded by

engrr_haris
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
143 views17 pages

5G NSA Call Drop Failures Possible Causes Troubleshooting Methods 1

5g drop call issues

Uploaded by

engrr_haris
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

5G NSA Release Signaling

“Call Drop Failures Possible Causes & Troubleshooting Methods”


NSA Series#2
CONTENT

SN Release procedure 5G Possible Root Causes


"Call Flow" of Retainability Issues

5G NSA Drop
Analysis Guide

Retainability identification 5G Call Drop related


from KPIs Parameters & Features
SN Release procedure(Normal Release)
The Following is the most common causes for the Normal Release messages
• MN Initiated SgNB Release Request includes Value Cause: radioNetwork: "User Inactivity“ or "MCG Mobility“.
• SN Initiated SgNB Release required includes Value Cause: readioNetwork: "User Inactivity“ or "SCG Mobility“ or "Action Desirable for Radio Reasons“.

Or it might include others cause such as "Handover Desirable for Radio Reasons", "Load Balancing“, etc.

SN Release procedure - MN initiated SN Release procedure - SN initiated

eNodeB gNodeB eNodeB gNodeB


UE S-GW MME UE S-GW MME
MN SN MN SN

1.SgNB Release 1.SgNB Release


Request Required

2.SgNB Release 2.SgNB Release


Request Ack Confirm

3.RRC Reconfiguration 3.RRC Reconfiguration

4.RRC Reconfig CMP 4.RRC Reconfig CMP

5. SN Status Transfer 5. SN Status Transfer

6. Data Forwarding 6. Data Forwarding

7. Secondary RAT 7. Secondary RAT


Data Volume Report Data Volume Report

8. Path Updte Procedure 8. Path Updte Procedure

9.UE Context Release 9.UE Context Release

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 - MN initiated SN Release procedure - SN initiated

eNodeB gNodeB eNodeB gNodeB


UE S-GW MME UE S-GW MME
MN SN MN SN

0. SCG Failure 1.SgNB Release


Information 1.SgNB Release Required
Request
2.SgNB Release 2.SgNB Release
Request Ack Confirm

3.RRC Reconfiguration 3.RRC Reconfiguration

4.RRC Reconfig CMP 4.RRC Reconfig CMP

5. SN Status Transfer 5. SN Status Transfer

6. Data Forwarding 6. Data Forwarding

7. Secondary RAT 7. Secondary RAT


Data Volume Report Data Volume Report

8. Path Updte Procedure 8. Path Updte Procedure

9.UE Context Release 9.UE Context Release

3GPP TS 37.340 version 15.5.0 Release 15 (Page 34 onwards)


3GPP TS 38.423 version 16.2.0 Release 16 (Page 221 to 223)
SN Release procedure (Normal Release due to Action-Desirable for Radio Network )

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

3GPP TS 38.423 definition


8. Path Updte Procedure
Radio Network
Meaning
9.UE Context Layer cause
Release
Handover Desirable for Radio Reasons The reason for requesting handover is radio related.

3GPP TS 37.340 version 15.5.0 Release 15 (Page 34 onwards)


3GPP TS 38.423 version 16.2.0 Release 16 (Page 221 to 223)
SN Release procedure (Normal Release due to MCG or SCG Mobility)
SN Release procedure - MN initiated

eNodeB gNodeB
UE S-GW MME
MN SN
1.SgNB Release
Non-Anchor
Request
2.SgNB Release
Request Ack
3.RRC Reconfiguration

4.RRC Reconfig CMP MN or SN


5. SN Status Transfer

6. Data Forwarding
7. Secondary RAT
Data Volume Report

8. Path Updte Procedure

9.UE Context Release

SN Release procedure - SN initiated

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

8. Path Updte Procedure 3GPP TS 38.423 definition


9.UE Context Release Radio Network
Meaning
Layer cause
MN Mobility The procedure is initiated due to relocation of the M-NG-RAN node UE context.
3GPP TS 37.340 version 15.5.0 Release 15 (Page 34 onwards) SN Mobility The procedure is initiated due to relocation of the S-NG-RAN node UE context.
3GPP TS 38.423 version 16.2.0 Release 16 (Page 221 to 223)
SN Release procedure (Normal Release due to SgNB User inactivity timer)
SN Release procedure - MN initiated

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

4.RRC Reconfig CMP


5. SN Status Transfer

6. Data Forwarding
7. Secondary RAT
Data Volume Report

8. Path Updte Procedure

9.UE Context Release

SN Release procedure - SN initiated

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

3GPP TS 37.340 version 15.5.0 Release 15 (Page 34 onwards)


3GPP TS 38.423 version 16.2.0 Release 16 (Page 221 to 223)
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues

Node Main Cause Possible Root-Causes Initiated By


• The detection of NR Radio Link Failure (RLF) can be carried
out by either the UE(MN) or the gNodeB (SN).
4G RRC Reestablishment Coverage and Quality issues

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:

The transmission over


Secondary 1. 4G RF issues (RRC Reestablishment)
Transport Transmission Fault the S1-U or X2-U
Node
interface is faulty

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

Maximum number of UL RLC


retransmissions in is reached
UL Interference
Master
7. Configuration issues.
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- 4G related

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues

The transmission over


Secondary
Transport Transmission Fault the S1-U or X2-U
Node
interface is faulty

Possible Root Causes of 5G UE UE Capability Issues Defects Ues


Secondary
Node
Retainability Issues

UE is in the uplink UL related timers


out-of-synchronization state
Secondary
Coverage, BLER, DL
Maximum number of DL RLC Node
Radio Condition PDCCH
retransmissions in is reached
Feature check

UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- Core related

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

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

The transmission over RRC Reconfiguration


Secondary
Transport Transmission Fault the S1-U or X2-U
Node RRC Reconfig CMP
interface is faulty Measurement Report
1.SgNB Addition Request
2.SgNB Addition Request
Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary
3.RRC Reconfiguration Ack
Node
Retainability Issues 4.RRC Reconfig CMP
SgNB Reconfig CMP

Random Access Procedure


UE is in the uplink UL related timers
out-of-synchronization state
Secondary
Maximum number of DL RLC
Coverage, BLER, DL E-RAB Modification Indication
Node
Radio Condition PDCCH
retransmissions in is reached Bearer Modification
Feature check
E-RAB Modification Confirm
UL Interference
RACH Configuration 1.SgNB Release Request
RA Problems during Cell Radius
Access or Handovers
Value Cause
No Dominanet Cell 2.SgNB Release Request
Ack RRM purpose
5G during HO

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- Transport

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues

The transmission over


Transport Transmission Fault the S1-U or X2-U
interface is faulty
SN or MN
*During HO

Possible Root Causes of 5G UE UE Capability Issues Defects Ues


Secondary
Node
Retainability Issues

UE is in the uplink UL related timers


out-of-synchronization state
Secondary
Coverage, BLER, DL
Maximum number of DL RLC Node
Radio Condition PDCCH
retransmissions in is reached
Feature check

UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- MAXDLRTXReached

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues UE eNodeB gNodeB

The transmission over ENDC Setup Completed


Transport Transmission Fault the S1-U or X2-U SN or MN
interface is faulty
RACH Procedure Completed

DL Packets
Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary
Node DL Packets DL Data
Retainability Issues DL Packets Transfer

UE is in the uplink UL related timers DL Packets


out-of-synchronization state
Secondary
Coverage, BLER, DL
Maximum number of DL RLC Node
Radio Condition PDCCH
retransmissions in is reached
Feature check
SgNB Release Required Drop due to
MAXDLRET
UL Interference SgNB Release X
confirm
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- RA Problems

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues
UE eNodeB gNodeB

The transmission over 1.SgNB Addition Request


Transport Transmission Fault the S1-U or X2-U SN or MN
interface is faulty 2.SgNB Addition Request
Ack ENDC
3.RRC Reconfiguration
Setup
CMP
Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary 4.RRC Reconfig CMP
Node SgNB Reconfig CMP
Retainability Issues
Random Access Preamble (MSG1)
UE is in the uplink UL related timers
out-of-synchronization state Random Access Response (MSG2)
RACH
Secondary
Coverage, BLER, DL Process
Maximum number of DL RLC Node
Radio Condition PDCCH Scheduled Transmission (MSG3)
retransmissions in is reached
Feature check

Contetion Resolution (MSG4)


UL Interference
RACH Configuration SCG Failure
RA Problems during Cell Radius Information
Access or Handovers No Dominanet Cell SgNB Release Request
Drop due to
5G during HO
2.SgNB Release Request
RAProblem
Ack
Maximum number of UL RLC
UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- MAXULRTXReached

Node Main Cause Possible Root-Causes Initiated By

4G RRC Reestablishment Coverage and Quality issues

Master
Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues UE eNodeB gNodeB

The transmission over


Transport Transmission Fault the S1-U or X2-U SN or MN ENDC Setup Completed
interface is faulty

RACH Procedure Completed


Possible Root Causes of 5G UE UE Capability Issues Defects Ues
Secondary
Node
Retainability Issues UL Packets

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

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Possible Root Causes of Retainability Issues- T310Expiry

Node Main Cause Possible Root-Causes Initiated By

UE eNodeB gNodeB

4G RRC Reestablishment Coverage and Quality issues

Master ENDC Setup Completed


Node
E-RAB Confirm not sent by the Core
Core (Value Cause RRM purpose)
Core Issues RACH Procedure Completed

DL Packets

The transmission over DL Packets DL Data


Transport Transmission Fault the S1-U or X2-U SN or MN DL Packets Transfer
interface is faulty T310
Expiry
DL Packets

Possible Root Causes of 5G UE UE Capability Issues Defects Ues


Secondary SCG Failure
Node Information
Retainability Issues SgNB Release Request Drop due to
2.SgNB Release Request T310 Expiry
Ack
UE is in the uplink UL related timers
out-of-synchronization state
Secondary
Coverage, BLER, DL
Maximum number of DL RLC Node
Radio Condition PDCCH
retransmissions in is reached
Feature check

UL Interference
RACH Configuration
RA Problems during Cell Radius
Access or Handovers No Dominanet Cell
5G during HO

Maximum number of UL RLC


UL Interference
retransmissions in is reached Master
Node
T310Expiry Coverage & Quality Issues
The UE fails to search for
cells (synchronization
SynRecgfail
failure, failure to receive
SSB)
RecfgFail Configuration or UE Issues
NSA Troubleshooting Guide: Retainability identification from KPIs

MN(UE)
5G Non-Standalone Drops Breakdown per MN & SN

Master Node

SN

Radio
DL MAX RLC
UE Lost UL SYN

Random values employed for visualization purposes only.


Secondary Node
NSA Troubleshooting Guide: 5G Call Drop related Parameters & Features

RACH Problems Layering Tuning

RACH
Cell Radius A2 RSRP for SgNB Release
Format

preambleReceivedTarget
Power powerRampingStep B1 Threshold for SgNB A5 Threshold for PScell
Addition Change
preambleTransMax

Downlink & UL RF Issues Abnormal Devices

RF Optimization DL & UL Max Retx


(DL & UL) Penalty Devices Blacklist from
Thresholds
Timers Core
"Mask IMEI-SV"
PDCCH Beamforming T310, n310 and n311
Feature(DL) Tuning
SPID Prohibit Access to 5G
UlTimeAlignmentTimer NSA from Radio

You might also like