5G Fall Back Procedure
5G Fall Back Procedure
5G Fall Back Procedure
There are two solutions of 5G Voice Evolution: EPS Fallback and 5G Voice over New Radio (VoNR).
5G voice is similar to the VoLTE process, except that PDU sessions need to be modified first to establish QoS flows for voice services.
Steps:
1.In UE calling or called scenario, IMS system triggers the QoS establishment process based on SIP signaling interaction.
2.5GC sends PDU session modification request to NG RAN.
3.NG RAN reconfigures the User Plane.
4.NG RAN returns the successful modification of the PDU session and informs 5GC, PCF, IMS.
5.The call continues, sends to the IMS domain, the same as the VoLTE process.
Introduction
A Network Operator providing 5G NR and 4G LTE service, but it may not be possible to have 5G coverage everywhere and at some point when 5G
coverage or service not available to 5G system (5GS) may attempt to fallback the RAT to 4G Evolved Packet System (4G-EPS). EPS Fallback can be
defined as the mobility procedure where network trigger the procedure for UE to change Radio Access from 5G to 4G.
We can see following fiugre showing the mobility profile for a UE performing mobility 5G to 4G, 4G to 4G and 4G to 5G. Here we can see the gNB and
eNB are co-located and gNB is operating on higher frequency band with lower coverage footprint and eNB operating on lower frequency band with larger
coverage footprint.
•Step#1RRC:MeasurementReport:UEsends MeasurementReport message to the source gNB including the serving cell and neighboring 4G cell signal strength as
indicated below.
Step#2 NGAP: HandoverRequired: After receiving the measurement report, the serving gNB check the reported 4G Cell PCI in neighbor relation table (NRT) and if
nieghbor is available it can initiate HandoverRequired message over N2 interface using NGAP protocol towards AMF. It includes UE identities (AMF-UE-NGAP-ID,
RAN-UE-NGAP-ID), Handover Type, Handover Cause, Target Cell ID, PDU session to be handover and Source to Target Transparent Container having the full UE
context and capabilities
•Step#3 gtp-v2: Forward Relocation Request: The serving AMF sent Forward Relocation Request to Target MME over the N26 interface using the gtp protocol. It
includes the IMSI, TEIDs, UE PDN information, Target Information and cause.
•Step#4 S1AP: HandoverRequest: The taget MME sends the Handover Request to target eNB including MME-UE-S1AP-ID, Handover Type, Hanodver Cause, E-RAB
information, Source to Target Transparent Container, UE Capabilities and UE security context.
•Step#5 S1AP: HandoverRequestAcknowledge: After receiveing the Handover request from MME, target 4G eNB start the UE admission procedure, if the resources are
available then eNB and respond with HandoverRequestAcknowledgement including UE IDs (MME-UE-S1AP, eNB-UE-S1AP), list of admitted e-RABs and Target to
Source Transport Container. If eNB does have enough resousrce to admit the UE, it can send Handover Failure with appropriate casue mentioning no resource available.
•Step#6: gtpv2: Forward Relocation Response: After Handover Acknownledge, the MME send Forward Relocation Response to 5G AMF
over N26 interface including the TEIDs and UE Bearer Context.
•Step#7: NGAP: HandoverCommand: AMF sends a Handover Command to source gNB. This message includes, information received in step#5 . The source gNB can
now send a Handover Command to the UE in step#8 as RRC message mobilityFromNRCommand. After receiving the Handover Command, the UE will leave the source
cell and start the connection towards the target 4G cell.
•Step#8: mobilityFromNRCommand: 5G gNB send it as the handover command to UE, it includes targetRAT-Type eutra, targetRAT Container and nas-
SecurityParamFromNR information.
•Step#8.a: RRCReconfiguration: UE RRC decodes target RAT container as RRCReconfiguration which have mobilityControlInfo indicating all 4G Target cell information
like carrier Bandwidth, UE-CRNTI as target, RACH config and other channel information.
•Step#9 RACH: A Random Access procedure is performed at the target eNB, considering the information recieved in step#8.a as part of rach-ConfigCommon or rach-
ConfigDedicated. rach-ConfigCommon used when eNB is not using dedicated premable for Handover and rach-ConfigDedicated is used when eNB is using dedicated
contention free RACH.
•Step#10 RRCReconfigurationComplete: After the UE has successfully connected to the target 4G cell, it completes the handover procedure by sending
the RRCReconfigurationComplete message to target eNB. UE starts Uplink data to Target eNB.
•Step#11 S1AP: HandoverNotify: Once UE has a successful RACH at 4G eNB and RRCReconfigurationComeplete is done then eNB inform the MME with HandoverNotify
indicating the HO is successful. It includes UE IDs (MME-UE-S1AP and eNB-UE-S1AP), Target Cell ECGI and Tracking Area Inforamtion.
•Step#12 gtpv2: ForwardRelocationCompleteNotification: As soon as MME recieved Handover Notify from Target eNB, the MME informs the AMF with Forward
Relocation Complete Notification over N26 interface indicated UE reached to 4G Target Cell and AMF can proceed with UE context clean-up at 5G System.
•Step#13 NGAP: UEContextReleaseCommand: By sending UEContextReleaseCommand AMF will instruct source gNB to release the resources related to this
UE. AMF in the message includes UE-NGAP-IDs to identify the UE context and cause indicating successful handover
•Step#14 gtpv2:ForwardRelocationCompleteNotificationAcknowledge: AMF send acknowledgement for Relocation Complete Notification as soon as it start UE
context cleanup procedure at 5G RAN and 5G Core.
•Step#15 NGAP:UEContextReleaseComplete: Source gNB sends UEConextReleaseComplete upon successful deleting the UE context and release all
the associated resource for the UE.
At last when UE successful handover to 4G Cell, it does perform the Tracking Area Update Procedure to update its current serveing Tracking Area.