E.4.4.1 IP-CAN Session Modification for EPC-routed traffic

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.4.1.1 PCRF-initiated IP-CAN Session Modification

This procedure is applicable both for WLAN and H(e)NB scenario.

Figure E.4.4.1.1.1: PCRF-Initiated IP-CAN Session Modification for EPC routed traffic

1 Step 1 to 3 as specified in figure 4.3.1.1.1 are executed. The H-PCRF receives an internal or external trigger to update PCC/QoS Rules. External trigger in Step 1 in figure 4.3.1.1.1 only applies to AF session interactions (as described in clause 4.3.1.2) and TDF session interactions (as described in clause 4.3.1.2). For V-PCRF initiated IP-CAN session modification, the V-PCRF always asks the H-PCRF for policy decision.

NOTE: If the AF/TDF is located in the V-PLMN, upon a request from the AF/TDF, the V-PCRF will proxy the request to the H-PCRF, this may also trigger the PCRF-Initiated IP-CAN Session Modification for EPC routed traffic.

2 The H-PCRF sends a Diameter RAR to update the QoS information to the BPCF.

If the UE is roaming, then steps 2a ~ 2c are executed instead of step 2:

2a. The H-PCRF sends a Diameter RAR to the V-PCRF to install, modify or remove PCC rules for Visited Access scenario, or QoS Rules for Home Routed scenario.

2b. The V-PCRF performs local authorization of the received PCC rules or QoS rules when necessary.

2c. The V-PCRF sends a Diameter RAR to the BPCF to update the QoS information.

3. The BPCF shall perform QoS validation and translates the QoS rule as received (i.e. SDF template, QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the BBF domain (the details of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the BBF domain is out of 3GPP scope).

4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation. If the BPCF cannot provide the requested QoS by the H-PCRF, the BPCF may respond with the acceptable QoS.

If the UE is roaming, then steps 4a ~ 4b are executed instead of step 4:

4a. The BPCF sends RAA to the V-PCRF to acknowledge the RAR and informs the V-PCRF about the outcome of the QoS rule operation. If the BPCF cannot provide the QoS requested by the V-PCRF, the BPCF may respond with the acceptable QoS.

4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation.

NOTE: If the H-PCRF is informed that the BPCF cannot provide the requested QoS, the H-PCRF can decide to install, modify or remove QoS rules. In that case, the same flow as described in this clause will be executed.

5. Step 5 to 12 as specified in figure 4.3.1.1.1 are executed.

E.4.4.1.2 BPCF-initiated IP-CAN Session Modification

This procedure is applicable both for WLAN and H(e)NB scenario.

Figure E.4.4.1.2.1: BPCF-Initiated IP-CAN Session Modification

1. The trigger for this procedure is that the Fixed Broadband Access has pre-empted some resources and wants to report a QoS rule failure to the PCRF, or when the Fixed Broadband Access network cannot sustain the bandwidth allocated to a particular traffic class/DSCP aggregate.

2. The BPCF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report QoS Rule failure.

When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2:

2a. The BPCF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report QoS Rule failure.

2b. The V-PCRF stores the information received.

2c. For Visited Access scenario, the V-PCRF sends a Diameter CCR to the H-PCRF to report PCC Rule failure. For Home Routed scenario, the V-PCRF sends a Diameter CCR to the H-PCRF to report QoS Rule failure.

3 The H-PCRF sends a Diameter CCA to the BPCF to acknowledge the CCR command.

When the UE is in roaming case, steps 3a ~ 3b are executed instead of step 3:

3a. The H-PCRF sends a Diameter CCA to the V-PCRF to acknowledge the CCR command.

3b. The V-PCRF forwards the Diameter CCA to the BPCF to acknowledge the CCR.

4. The PCRF-initiated IP-CAN Session Modification as described in E.4.4.1.1 may take place.

E.4.4.1.3 PCEF-initiated IP-CAN Session Modification

This procedure is applicable both for WLAN and H(e)NB scenario.

Figure E.4.4.1.3.1: PCEF-Initiated IP-CAN Session Modification

1. Step 1 to 3 (3a-3c for the Visited Access case) is the same as specified in figure 4.3.2.1.1. In step 3 (3c for the Visited Access case), when the UE Local IP address, H(e)NB Local IP address or the UDP port number is changed, the PCEF may provide the updated UE local IP address, the updated H(e)NB IP address, and/or UDP port number if available, to the PCRF; or the PCEF cannot enforce the PCC rule(s) and need report the PCC rule failure to the PCRF.

2. The H-PCRF sends a Diameter RAR to request that the BPCF installs, modifies or removes QoS Rules (i.e. SDF template, QCI, ARP, MBR and GBR).

When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2:

2a. For Visited Access scenario, the H-PCRF may provision the PCC rule(s) to the V-PCRF. For Home Routed scenario the H-PCRF may provision the QoS rule(s) to the V-PCRF. The H-PCRF may provision for WLAN case the UE local IP address, and UDP port number (if available) and for H(e)NB case the H(e)NB local IP address, and UDP port number (if available) to the V-PCRF.

2b. The V-PCRF performs local authorization of the QoS Rules or PCC rules when necessary.

2c. The V-PCRF may provision QoS rules to the BPCF by using RAR command. The V-PCRF may provision for WLAN case the UE local IP address, and UDP port number (if available) and for H(e)NB case the H(e)NB local IP address, and UDP port number (if available) to the BPCF.

3 The BPCF shall perform QoS validation and translates the QoS information as received (i.e. QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the Fixed Broadband Access.

NOTE The detail of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the Fixed Broadband Access is out of 3GPP scope.

4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR command. If the QoS validation for admission control fails, the BPCF may include the acceptable QoS in the Fixed Broadband Access using 3GPP QoS parameters on S9a interface.

When the UE is in roaming case, steps 4a ~ 4b are executed instead of step 2:

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

4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR command.

5. Step 4 to 18 is the same as specified in figure 4.3.2.1.1.

E.4.4.1.4 BBERF-initiated IP-CAN Session Modification

This procedure is applicable for both WLAN and H(e)NB scenario.

Figure E.4.4.1.4.1: BBERF-Initiated IP-CAN Session Modification

1 Step 1 to 3(3a-3c for the Visited Access case) is the same as specified in figure 4.3.2.1.1.

In step 1, in case 2b and case 2a for WLAN scenario, when the UE Local IP address, and/or the UDP port number is changed, the BBERF (ePDG) may provide these information to the PCRF. For H(e)NB scenario, when the H(e)NB local IP address and the UDP port number is changed, the BBERF (S-GW) may provide these information to the PCRF.

2 The H-PCRF sends a Diameter RAR to request that the BPCF installs, modifies or removes QoS Rules (e.g. SDF template, QCI, ARP, MBR and GBR).

When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2:

2a. For Visited Access scenario, the H-PCRF may provision the PCC rule(s) to the V-PCRF. For Home Routed scenario the H-PCRF may provision the QoS rule(s) to the V-PCRF. The H-PCRF provisions for WLAN case the UE local IP address and/or UDP port number, and for H(e)NB case the H(e)NB local IP address and UDP port number to the V-PCRF.

2b. The V-PCRF performs local authorization of the QoS Rules or PCC rules when necessary.

2c. The V-PCRF may provision QoS rules to the BPCF by using RAR command. The V-PCRF provisions for WLAN case the UE local IP address and/or UDP port number, and for H(e)NB case the H(e)NB local IP address and/or UDP port number to the BPCF.

3 The BPCF shall perform QoS validation and translates the QoS information as received (i.e. QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the Fixed Broadband Access.

NOTE: The detail of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the Fixed Broadband Access is out of 3GPP scope.

When the UE is in roaming case, steps 4a ~ 4b are executed instead of step 4:

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

4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR.

5. Step 4 to 18 is the same as specified in figure 4.3.2.1.1.