E.4.3 IP-CAN Session Termination

29.2133GPPPolicy and charging control signalling flows and Quality of Service (QoS) parameter mappingRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

E.4.3.1 IP-CAN Session Termination for EPC- routed traffic

Figure E.4.3.1.1: IP-CAN Session Termination for EPC-routed traffic

1. Perform the step 1 through step 3: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN, step 1 through step 5: as defined in Figure 4.2.2.1: PCEF-initiated IP-CAN session termination-AF located in HPLMN or step 1 through step 8: as defined in Figure 4.2.3.1: PCRF-initiated IP-CAN session termination-AF located in HPLMN.

2. For GTP/PMIP-based S2b of the WLAN scenario (non-roaming case), triggered by a Gateway control session termination from BBERF(ePDG) or by an Indication of IP-CAN session termination from PCEF, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session.

For trusted and untrusted S2c of the WLAN scenario (non-roaming case), triggered by the Indication of IP-CAN session termination, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this user; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection.

For H(e)NB scenario (non-roaming case), triggered by a Gateway control session termination from BBERF(S-GW) or by an indication of IP-CAN session termination, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when last PDN connection is released for this H(e)NB Local IP address; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection.

For case 1 (roaming with home routed case), the steps 2a and step 2b are executed instead of step 2.

2a. If the subsession being terminated is the last subsession over S9, the H-PCRF sends a RAR including the Session-Release-Cause AVP to the V-PCRF to indicate the termination of the S9 session. Otherwise, the H-PCRF sends a RAR to the V-PCRF including the Subsession-Decision-Info AVP with the Session-Release-Cause AVP to indicate the request for terminating the S9 subsession corresponding to the IP-CAN session.

2b. For GTP-based S2b of the WLAN scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session.

For trusted S2c of the WLAN scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session when the last PDN connection is released for this user; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection.

For the H(e)NB scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session when the last PDN connection is released for this H(e)NB Local IP address; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection.

For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 2c is executed instead of step 2.

2c. For GTP/PMIP-based S2b of the WLAN scenario, triggered by a Gateway control session termination from BBERF(ePDG) or by an Indication of IP-CAN session termination, the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session.

For trusted and untrusted S2c of the WLAN scenario, triggered by the Indication of IP-CAN session termination or S9 session/subsession termination request from the H-PCRF , the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this user; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection

For case 1 and case 2b of H(e)NB scenario, triggered by a Gateway control session termination from the BBERF(S-GW) or by an Indication of IP-CAN session termination, the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this H(e)NB Local IP address; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection.

3. For the non-roaming case, the BPCF sends a RAA to acknowledge the RAR.

For case 1 (roaming with home routed case), the steps 3a and 3b are executed instead of step 3.

3a. The BPCF sends a RAA to the V-PCRF.

3b. The V-PCRF sends a RAA to the H-PCRF.

For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 2c is executed instead of step 2.

3c. The BPCF sends a RAA to the V-PCRF.

4. For the non-roaming case, the BPCF sends a CCR to the H-PCRF to indicate the S9a session termination if the H-PCRF requests that the BPCF terminates the S9a session in step 2. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION_REQUEST.

For case 1(roaming with home routed case), the steps 4a and 4b are executed instead of step 4

4a. The BPCF sends a CCR to the V-PCRF to indicate the S9a session termination if the V-PCRF requests that the BPCF terminates the S9a session in step 2b. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION_REQUEST.

4b. The V-PCRF sends a CCR to the H-PCRF to indicate the S9 session termination if the H-PCRF requests that the V-PCRF terminates the S9 session in step 2a. The V-PCRF requests the termination of the S9 session using the CC-Request-Type set to the value TERMINATION_REQUEST.

For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 4c is executed instead of step 4.

4c. The BPCF sends a CCR to the V-PCRF to indicate the S9a session termination if the V-PCRF request that the BPCF terminates the S9a session in step 2c. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION_REQUEST.

5. For the non-roaming case, the H-PCRF sends a CCA to acknowledge the CCR.

For case 1 (roaming with home routed case), the steps 5a and 5b are executed instead of step 5

5a. The H-PCRF sends a CCA to acknowledge the CCR.

5b. The V-PCRF sends a CCA to acknowledge the CCR.

For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 5c is executed instead of step 5.

5c. The V-PCRF sends a CCA to acknowledge the CCR.

6. Perform the step 3 through step 7: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN,

7. Perform the step 8 through step 11 :As Specified in Figure 4.2.1.1 for AF located in HPLMN or step 2 through step 9 :as specified in Figure 4.2.1.2 for AF located in VPLMN

8. Perform the step 12 through step 15: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN.

E.4.3.2 IP-CAN Session Termination for NSWO traffic

E.4.3.2.1 BPCF-initiated IP-CAN Session Termination for NSWO traffic

Figure E.4.3.2.1.1: BPCF-initiated IP-CAN Session Termination for NSWO Traffic

1. The Fixed Broadband Access network is aware of the UE is detached from the broadband access network

2. For the non-roaming case, the BPCF sends a CCR to the H-PCRF to indicate the S9a* session termination. The BPCF requests the termination of the S9a* session using the CC-Request-Type set to the value TERMINATION_REQUEST.

For the roaming case, the steps 2a and 2c are executed instead of step 2.

2a. The BPCF sends a CCR to the V-PCRF to indicate the S9a* session termination. The BPCF requests the termination of the S9a* session using the CC-Request-Type set to the value TERMINATION_REQUEST.

2b. If there is an active TDF session between TDF and V-PCRF, the TDF session termination is initiated as defined in clause 4.6.2. For this case, the PCRF described in clause 4.6.2 acts as a V-PCRF.

2c. The V-PCRF sends the CCR to the H-PCRF. If this is the last subsession associated with the S9 session, the V-PCRF sends a CCR to the H-PCRF to request the termination of the S9 session using the CC-Request-Type AVP set to the value TERMINATION_REQUEST. Otherwise, the V-PCRF sends a CCR to the H-PCRF with a CC-Request-Type AVP set to the value UPDATE_REQUEST and a Subsession-Enforcement-Info within which the Subsession-Operation AVP set to value TERMINATION to request the termination of the conresponding S9 subsession.

3. The H-PCRF identifies the AF sessions that are bound to IP flows of the removed IP-CAN Session.

4. For the non-roaming case, the H-PCRF acknowledges the S9a* session termination by sending a CCA to the BPCF.

For the roaming case, steps 4a~4c are executed instead of step 4:

4a. The H-PCRF acknowledges the S9 session or subsession termination by sending a CCA to the V-PCRF.

4b. The V-PCRF removes the information related to the terminated IP-CAN Session.

4c. The V-PCRF acknowledges the S9a* session termination by sending a CCA to theBPCF.

5. If there is an active TDF session between TDF and H-PCRF, the TDF session termination is initiated as defined in clause 4.6.2.

6. Perform step 8 through step 12: as specified in Figure 4.2.1.1: UE-Initiated IP-CAN Session Termination – AF located in the HPLMN

E.4.3.2.2 PCRF-initiated IP-CAN Session Termination for NSWO traffic

Figure E.4.3.2.2.1: PCRF-initiated IP-CAN Session Termination for NSWO Traffic

1. The H-PCRF detects that the termination of an IP-CAN Session is required.

2. For the non-roaming case, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a* session.

For the roaming case, steps 2a~2b are executed instead of step 2:

2b. The V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF.

3. The Fixed Broadband access network removes all the PCC rules which are applied to the IP-CAN session.

4. For the non-roaming case, the BPCF sends a RAA to acknowledge the RAR.

For the roaming case, steps 4a~4b are executed instead of step 4:

4a. The BPCF sends a RAA to the V-PCRF.

4b. The V-PCRF sends a RAA to the H-PCRF and acknowledges the request for terminating the S9 session or the S9 subsession corresponding to the IP-CAN session.

5. Step 2 through 6: as specified in Figure E.4.3.2.1.1:BPCF-initiated IP-CAN session termination for NSWO traffic.