Content for  TS 23.402  Word version:  18.3.0

The procedure in this clause applies to both Detach Procedures, including UE or Trusted non-3GPP access initiated detach procedure, and UE/Trusted non-3GPP Access requested PDN disconnection procedure when supported by the Trusted non-3GPP access. The UE can initiate the detach procedure, e.g. when the UE is power off. The Trusted Non-3GPP Access Network can initiate the detach procedure due to administrative reasons or detecting the UE's leaving by, e.g. Link-layer event specific to the access technology (refer to PMIPv6 specification, RFC 5213, for more information).

For detach procedure and in case of connectivity with multiple PDNs, the steps 2 to 6 are repeated for each PDN the UE is connected to. For UE-requested PDN disconnection procedure, steps 2 to 6 are performed for the PDN that the UE requested disconnection from. This procedure applies to the Non-Roaming (Figure 4.2.2-1), Roaming (Figure 4.2.3-1) and Local Breakout (Figure 4.2.3-4) cases. For the Roaming and Local Breakout cases, the vPCRF forwards messages between the non-3GPP access and the hPCRF. In the Local Breakout case, the vPCRF forwards messages between the PDN-GW and the hPCRF. In the Roaming and LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming case, the vPCRF is not involved at all. If dynamic policy provisioning is not deployed, the optional steps of interaction between the gateways and PCRF do not occur. Instead, the PDN-GW may employ static configured policies.

This clause defines the UE/Trusted Non-3GPP IP Access Network-initiated detach procedure UE-requested PDN disconnection procedure for PMIP-based S8-S2a chaining. This procedure also applies to UE/ePDG-initiated detach procedure for PMIP-based S8-S2b chaining.

For detach procedure and in case of connectivity with multiple PDNs, the steps 2 to 7 are repeated for each PDN the UE is connected to. For UE-requested PDN disconnection procedure for chained PMIP-based S8-S2a, steps 2 to 7 are performed for the PDN that the UE requested disconnection from.

HSS/AAA-initiated detach procedure with PMIPv6 is illustrated in Figure 6.4.2.1-1. The HSS can initiate the procedure e.g. when the user's subscription is removed. The 3GPP AAA Server can initiate the procedure, e.g. instruction from O&M, timer for re-authentication/re-authorization expired. If the HSS/AAA-initiated detach procedure has been initiated to delete the UE from the Evolved Packet Core, the HSS/AAA server shall initiate the detach procedure for each of the access systems to which the UE is registered.

This procedure applies to the Non-Roaming (Figure 4.2.2-1), Roaming (Figure 4.2.3-1) and Local Breakout (Figure 4.2.3-4) cases. For the Roaming and Local Breakout cases, the vPCRF forwards messages between the non-3GPP access and the hPCRF. In the Local Breakout case, the vPCRF forwards messages between the PDN-GW and the hPCRF. In the Roaming and LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming case, the vPCRF is not involved at all.

This clause defines the HSS/AAA-initiated detach procedure for PMIP-based S8-S2a chaining. This procedure also applies for PMIP-based S8-S2b chaining. If the HSS/AAA-initiated detach procedure has been initiated to delete the UE from the Evolved Packet Core, the HSS/AAA server shall initiate the detach procedure for each of the access systems to which the UE is registered.