VOLTE MOC Call Failed due to Insufficient Bearer Resources

In XXX Project in YYY Country VOLTE Call Failure due to

Insufficient Bearer Resources

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

1- Problem Description
In XXX Operator in YYY Country we received VVIP Complain, Related to VOLE Call Failure, where
as it was this is V2C call.

(Dedicated Bearer was failure due to no response from eNodeb to Modify EPS Bearer context
request sent by MME)

2- Verifications:
Once we received the Complain we established a room invited all the team members belongs to
this issue , we exported PCAB Trace File from third Party (Asetelia) , Mean while we collected
the Board Log of the serving site according the complain Time.

IMS Feedback

PS Feedback

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

3- Handling Steps
 Alarm Log
 OPT Log
 Signaling trace
 KPI

Alarm Log
NA (No Record)
Operation log
NA (No Record during the Time of Degradation)
Signaling trace analysis
We got PCAB Trace file from third Party includes all domains and Open by Wire shark as
Unfortunately No life Trace was open during the Problem so we can depend on the trace file
generated by Aseteliah by the aid of Nastar and Board Log as well.

As we mentioned earlier we expected that due to Dedicated Bearer failure which has been
reported cause of no response from eNodeb to Modify EPS Bearer context request sent by
MME)

As Per Bellow Procedure of ERAB Setup Modify, Bellow Points will describing our Findings..

 After Setup established ERAB by MME Then ENODEB Sent Response , after that Uplink NAS
Transport Request (bearer extended) →triggered CSFB, Then MME Should send Modify
Bearer , which by anyhow did not received by ENODEB , which means no Modification of
ERAB Triggered by eNodeb to forwarded to UE.

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

 This time MME Send three Times NAS Layer Uplink towards which is not received by
ENODEB
 UE Context release sent by ENODEB towards MME @ 21:30 40 .
 UE Context Release sent by ENODEB Showing “Radio with UE Connection Lost” which needs
Confirmation By MR Logs of served Site 1560 during the Call.
 Checking UU and S1 interface trace during the Time of the issue, we can find that ENODEB
did not receive the MME Modify Bearer, after MR report which is the time of sending the
Modification From MME then Release UE sent by ENODEB.
 Radio Conditions As per MR report are verifying badly during the Timing Issue for RSRP , SNR
Which may leads this issue as the failure UE with Radio Connection Lost(HO Failure).
 Then we Checked RTT Delay on SCTP Layer to check If the date sent by the frame is same as
Received data during the Call, we found 7 frames Lost comparing Send and Received frames,
with very High RTT Delay .
 Radio KPIs did not show any Failure in ERAB Modify showing bellow.

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

Trace Procedure Update summery.

1. @ 21:30:03 61651 UE is Successfully Established QCI1 To Proceeded on VOLTE Call
Setup.
2. @21:30:06 373642, 183 Session Progress sent from HSS To SCSF Then ATS Then SCSF To
SBC, SBC To PCRF To UGW then MME To Modify EPS Bearer
3. @21:30:06 52828 MME sent ERAB Modify bearer to ENODEB and UE in S1 NAS
Transport, but Neither ENODEB or UE received the NAS Massage which can be noticed in
NASTAR during this Time.
4. @21:30:14 529337 MME Resent DL NAS Transport to Modify EPS Bearer.
5. @21:30:22 551805 SBC Has Canceled the Call with Cause Code 503 Insufficient Bearer
Resources.
6. @21:30:22 518308 MME Has Deactivated EPS Bearer but the this Massage DID NOT
Receive by ENODEB and or UE, which can be noticed on NASTAR trace Signaling MSGs
7. @21:30:40 916901 ENODEB is requesting from MME to Release the Context with UE for
UE with Radio Connection Lost.

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

8. @21:3051 3025 Had resent DL NAS Deactivate EPS Bearer however it is not received by
ENODEB and or UE , which already confirmed by Signaling Trace on Nastar, although we
could not Find on the TRACE
9. 503 Should be triggered then Normal Procedure of CSFB is done
During the Timing In between 21:30:03 616511 ⌠21:30:35n878000 → In 3G Service without
sending CM Extended SERVICE Request Which means MS Has Improper Teardown from 4G to
3G Regardless MS Type

 Bellow Figures confirm that UE did not receive the Deactivation OF Bearer First One
Deactivate QC1, Second one Act QC 5,9,1 However QCI1 Should be deactivated during 3G .

Nastar:

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

CHR Logs

RTT Conditions:

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

Hany Mohamed kamel 00312667

VOLTE MOC Call Failed due to Insufficient Bearer Resources

KPIS Verification
NO Fail in ERAB Modification and it is remain Zero.

Conclusion

1-Bad Coverage (HO failure)

2-High RTT delay with Frame date Lost (Tunnel In between eNodeB and MME)

a/m causes are the main raison for the abnormal UE behavior causing the VOLTE Call Failure.

Hany Mohamed kamel 00312667