Project

General

Profile

Actions

Bug #6333

closed

Describe UE/ePDG-initiated Detach Procedure

Added by pespin 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
01/18/2024
Due date:
% Done:

90%


Description

Related: 3GPP TS 23.402 section 7.4 "Detach and PDN Disconnection for S2b", and specifically section "7.4.3 UE/ePDG-initiated Detach Procedure and UE-Requested PDN
Disconnection with GTP on S2b".

That section explains (vaguely) that the UE can initiate a procedure to detach from ePDG. Sequence diagram Figure 7.4.3-1 refers to "Detach procedure as in Figure
7.4.1-1, before step (A)", which state: "IKEv2 tunnel release trigger".

lynxis can you clarify what does that exactly mean/involve at strongswan side between UE<->strongswan? Not sure if you already looked at / though about this scenario.
We probably also need to define messages between strongswan <> osmo-epdg to forward this.
Again, not sure if you need a response ePDG->strongswan you can answer the UE, please provide feedback here. According to Figure 7.4.1-1, we need a "6. Non-3GPP specific
resource release procedure".

Finally, once we figure the message type in CEAI, we have to implement in osmo-epdg:
- Tx DeleteSessionReq to PGW
- Rx DeleteSessionResp from PGW


Checklist

  • Find out message for "IKEv2 tunnel release trigger" to act in strongswan and forward through CEAI to osmo-epdg
  • Define message for GSUP CEAI interface to release a tunnel (EPDGTunnelReleaseReq/Resp?)
  • Do GTPv2C DelelteSessionReq/Resp osmo-epdg<>PGW
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)