Content for  TS 23.402  Word version:  18.3.0

The procedure in this clause applies to both UE initiated Detach Procedure and UE-requested PDN disconnection procedure with MIPv4 FACoA when supported by the Trusted non-3GPP access. The UE can initiate this procedure, e.g. when the UE is powered off.

For detach procedure and in case of connectivity with multiple PDNs, the steps 1 to 9 are repeated for each PDN the UE is connected to. For UE-requested PDN disconnection procedure, steps 1 to 9 are performed for the PDN that the UE requested disconnection from. The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway. 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.

Trusted Non-3GPP Access Network initiated detach procedure with MIPv4 FACoA Mode is illustrated in Figure 6.4.4-1. The Trusted Non-3GPP Access Network can initiate this procedure due to administration reason or detecting the UE's leaving by, e.g. Link-layer event specific to the access technology (see RFC 3543 for more information).

The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway. 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.

HSS/AAA-initiated detach procedure with MIPv4 FACoA Mode is illustrated in Figure 6.4.5-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.

The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway. 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.