E.4.2 IP-CAN Session Establishment

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.2.1 IP-CAN Session Establishment for EPC- routed traffic

This procedure is applicable for WLAN and H(e)NB scenarios for EPC-routed traffic. This procedure is same as described in clause 4.1 with the exceptions described in this clause.

Figure E.4.2.1.1 IP-CAN Session Establishment for EPC-routed traffic

1. Step 1 through step 6: as specified in Figure 4.1.1: IP-CAN session establishment are executed towards the H-PCRF (non-roaming case or home routed case) or towards the V-PCRF (roaming case).

For case 2a and case 2b of the WLAN scenario and for case 2b of the H(e)NB scenario, the BBERF provides the data as described in 3GPP TS 29.212 [9], clause E.5.2.

For case 1, the PCEF provides the data as described in 3GPP TS 29.212 [9], clause E.5.1.

For case 1 (visited access), case 2a and case 2b (home routed and visited access) the V-PCRF forwards the data towards the H-PCRF.

NOTE: For the roaming case, the V-PCRF omits the UE Local IP address (WLAN scenario), the H(e)NB Local IP address and the UDP port in the S9 reference point.

2. For GTP/PMIP-based S2b of the WLAN scenario (non-roaming case) the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment or Indication of IP-CAN session establishment in step 1.

For trusted and untrusted S2c of the WLAN scenario (non roaming case), when there is not an already established S9a session for the user, the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment in step 1; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF.

For H(e)NB scenarion (non roaming case), when there is not an already established S9a session for the H(e)NB Local IP address, the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment or Indication of IP-CAN session establishment in step 1; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF.

The PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1

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

2a. If there is not an already established S9 session for the user, the H-PCRF sends a TER command to V-PCRF to trigger an S9 session establishment procedure triggered by the Indication of IP-CAN session establishment in step 1; otherwise, the H-PCRF sends a RAR command to V-PCRF to trigger an S9 subsession establishment procedure.

The H-PCRF trigger an S9 session/subsession establishment procedure as described in 3GPP TS 29.215 [22], clause A.6.1.1.1 or A.6.3.1.0.

2b. For GTP-based S2b of the WLAN scenario, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure.

For trusted S2c of the WLAN scenario, if there is not an already established S9a session for the user, the V-PCRF sends a TER command to BPCF; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF.

For the H(e)NB scenario and if there is not an already established S9a session for the H(e)NB local IP address, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise the V-PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF.

The V-PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1.

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 trusted and untrusted S2c of the WLAN scenario when there is not an already established S9a session for the user, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF.

For GTP/PMIP-based S2b of the WLAN scenario the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure.

For case 1 and case 2b of the H(e)NB scenario when there is not an already established S9a session for the H(e)NB local IP address, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise, the V-PCRF may send a RAR command to provide the QoS rules to the BPCF.

The V-PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1.

3. The BPCF acknowledges to the PCRF by sending the TEA /RAAcommand.

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

3a. The BPCF acknowledges to the V-PCRF by sending the TEA /RAAcommand.

3b. The V-PCRF acknowledges to the H-PCRF by sending the TEA/RAA command.

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

3c. The BPCF acknowledges to the V-PCRF by sending the TEA/RAA command.

4. For the non-roaming case, triggered by step 2, the BPCF initiates an S9a session establishment with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value INITIAL_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.

For case 1 (roaming with home routed case), the steps 4a~4c are executed instead of step 4.

4a. Triggered by step 2b, the BPCF initiates an S9a session establishment with the V-PCRF by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.

4b. The V-PCRF determines that the request is for a roaming user and stores the received information.

4c. If there is not an already established S9 session for the user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT.

For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), the steps 4d~step 4e are executed instead of step 4.

4d. Triggered by step 2c, the BPCF initiates an S9a session establishment with the V-PCRF by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.

4e. The V-PCRF determines that the request is for a roaming user and stores the received information.

5. The H-PCRF stores the information received in the CCR.

6. For the non-roaming case, the H-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF.

For case 1 (roaming with home routed case), steps 6a~6b are executed instead of step 6.

6a. The H-PCRF acknowledges the S9 session establishment/modification by sending a CCA to the V-PCRF.

6b. The V-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF.

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

6c. The V-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF.

7. Step 7 through step 15: as specified in Figure 4.1.1: IP-CAN session establishment are executed. Step 13 is only applicable to case 2b of H(e)NB scenario.

E.4.2.2 IP-CAN Session Establishment for NSWO traffic

Figure E.4.2.2.1: IP-CAN Session Establishment for NSWO traffic

1. The broadband access network becomes aware of the IMSI of the 3GPP UE if 3GPP-based access authentication (EAP-AKA/AKA’) is performed. The BPCF also becomes aware of the UE local IP address.

2. For the non-roaming case, the BPCF initiates an S9a* session establishment procedure with the H-PCRF by sending a CCR using the CC-Request-Type AVP set to the value INITIAL_REQUEST. The BPCF shall provide the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.1.

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

2a.The BPCF initiates an S9a* session establishment procedure with the V-PCRF by sending a CCR to the V-PCRF using the CC-Request-Type AVP set to the value INITIAL_REQUEST. The BPCF shall provide the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.1.

2b. The V-PCRF determines that the request is for a roaming user and stores the received information.

2c. If there is not an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT.

If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT.

3. The H-PCRF stores the information received in the CCR.

4. Perform step 5 through 11: as specified in Figure 4.1.1: IP-CAN session establishment. Additionally, an indication on whether policy control for NSWO traffic should be performed for the UE may be retrieved from the SPR. The H-PCRF enables policy control for NSWO traffic for that UE based on operator policies and user profile information that may depend on e.g. NSWO-APN being used by the UE.

5. For the non-roaming case, the H-PCRF provisions the PCC Rules to the BPCF using CCA if policy control is enabled.

For the roaming case, steps 5a~5f are executed instead of step 5.

5a. The H-PCRF provisions the PCC Rules if available to the V-PCRF using CCA if policy control is enabled. The H-PCRF includes PCC Rules and ADC Rules if available in the Subsession-Decision AVP of the CCA, along with the S9 subsession identifier as received in step 2c within the Subsession-Id AVP.

5b. If policy control is enabled in step 5a, the V-PCRF stores the received PCC rules if available. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements.

5c. The V-PCRF informs the H-PCRF when a request has been denied and may provide the acceptable QoS information for the service.

5d. The H-PCRF acknowledges the CCR and may additionally include new or modified PCC rules to the V-PCRF. When user profile configuration indicates that Application Detection and Control function is enabled, the H-PCRF may additionally include new or modified PCC rules for application detection and control.

5e. In case of solicited application reporting with a TDF, the V-PCRF initiates a TDF Session Establishment procedure, according to clause 4.6.1, with the selected TDF.

5f. The V-PCRF provisions PCC rules received from the H-PCRF to the BPCF by using CCA.