5GS-WiFi(ePDG) Calling/Offloading Aspects

1       EPDG <–>5GS IMS Media (Voice/Video) Offloading

1.1     Introduction

We already have seen about IMS Media Voice / Video etc offload to ePDG from EPS to seek better Quality coverage and throughput and Seamless experience for Video / Voice calls in a closed environment like In-house, office, etc where User can access good WiFi coverage than EPS. To get same kind of good quality coverage experience in epDG <–> 5GS HO deployment, I have covered possible call flows with required changes in IKE_AUTH and 5GS message to support these scenarios. We will not cover N3IWF <–> 5GS Handover scenarios in this document now and will cover it in the future.

1.2     Technical Aspect and Interfaces

1.2.1     General

WLAN 5 standard and above (WLAN 6 and WLAN 6E) are preferred to do better seamless HO between eDPG ßà 5GS.  802.11ax is highly desirable as a WLAN standard.

1.2.2     Interworking Architecture between ePDG <–> 5GS

1.2.3     Pre-Requisite

To Simplify and for better understanding, I have taken case as UE is 3GPP REGISTERED with 5GS in upcoming sections. Furthermore,  There is N26 interface between AMF and MME present and UE support only Single Registration mode only.

  1. If UE is Registered with 3GPP EPS than during ePDG -> 5GS HO, UE will initiate RegistrationRequest on 5G with “requesttype” as “Mobility Registration” in Single Registration mode.
  2. If UE support Dual Registration mode than UE will initiate RegistrationRequest on 5G with “requesttype” as “initial Registration

1.3     5GS –> epDG IMS Media Offloading

1.3.1     3GPP defined Call Flow as per 23.502

1.3.2     General Call Flow

  1. UE is registered with 5GS and IMS and Internet PDU session established. Voice  / Video / RTT call is successfully established on 5GS.
  2. NW measure WLAN / ePDG power and find good WLAN power, which is appropriate to do Voice / Video offload on ePDG.
  3. ePDG DNS message exchanged and UE gets ePDG Tunnel information.
  4. IKE_SA_INIT Procedure on epDG start to get Encryption algos and other epDG policies exchange.
  5. In IKE_AUTH_Req , UE inform NW about N1_Mode_Capabilty with PLMN info which are equivalent to 5GS and ongoing PDU_Session_ID . Same PCO information ( Port, UE IP, etc) as used in 5GS will be reused.
  6. In IKE_AUTH_RESP, NW will provide N1_Mode_Information with S-NSSAI information and equivalent PLMN ID and other default parameters ( same as used in EPS).
  7. IMS PDU session on 5GS released.
  8. Once EAP-AKA IKEV2 procedure completed. UE will initiate IMS Re-Registration on epDG
  9. IMS Voice/ Video/RTT call offload from 5GS to epDG.

1.4     ePDG–> 5GS IMS Media HO

1.4.1     3GPP defined Call Flow as per 23.502

1.4.2     General Call Flow

  1. UE is 5GS 3GPP Registered and Internet PDU session established.
  2. IMS PDU and Media (Voice, Video, RTT) are established on ePDG and RTP date for Video / Audio are flowing on ePDG.
  3. In IKE_AUTH message, UE is already provided N1 Mode capability / information to NW about N1 Mode support .
  4. ePDG power reduced below to threshold and 5G RAN power increased.
  5. UE will send PDU Session Establishment Req for IMS DNN with requesttype as “existing PDU Session” and same PCO information (UE IP, port etc, ) to 5GS.
  6. NW will respond with PDUSessionAccept with same PCO information and 5QI as 5 and other QoS Flow information as required  for IMS PDU Session .
  7. IMS Re-Registration procedure happened on 5GS with PANI as “NR-FDD”.
  8. PDU Modification command from NW with 5QI =1 and other QoS Rules to established Voice completed.
  9. Voice Media RTP packets started on 5GS between UE and 5GS.
  10. IMS PDU ePDG tunnel release between UE-epDG.

1.5     ePDG –> 5GS –> EPS Fallback case

1.5.1     3GPP defined Call Flow as per 23.502

1.5.2     General Call Flow

  1. Please follow till step 7 of section 1.4.2
  2. UE may send Re-INVITE to establish and request Dedicated Voice QoS Flow on 5GS and set PANI as “3GPP-NR-FDD” .
  3. NW will decide to do Fallback Voice / video on EPS during Voice QoS Flow establishment.
  4. Voice Media RTP may be paused or go on default IMS PDU Session for some time until dedicated bearer / QoS flow not established.
  5. Please follow EPS Fallback procedure for Voice establishment on EPS.
  6. After Voice call ends on EPS , UE will do either Redirection or Reselection to move back to NR.

1.6     References

  • 24.501
  • 23.502
  • 23.402
  • 24.302
  • 23.501