4.4.2 Gateway Control and QoS Rules Request

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

4.4.2.1 Non-Roaming and Home Routed cases

Figure 4.4.2.1.1: Gateway Control and QoS Rules Request for non-roaming and home routed

1. The BBERF is triggered to either report an event or obtain QoS rules or both for a gateway control session.

2. The BBERF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report event or request QoS rules.

When the UE is roaming (home routed traffic), steps 2a ~ 2c are executed instead of step 2:

2a. The BBERF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report event or request QoS rules.

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

2c. For case 2a, The V-PCRF sends a Diameter CCR to the H-PCRF within the information received in step 2a at command level.

For case 2b, The V-PCRF sends a Diameter CCR to the H-PCRF within the information received in step 2a at Subsession-Enforcement-Info AVP.

3. The H-PCRF stores the received information in the Diameter CCR and derives updated QoS rules and event triggers.

4. The H-PCRF provisions the updated QoS rules and event triggers to the BBERF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully.

When the UE is roaming (home routed traffic), steps 4a ~ 4c are executed instead of step 4:

4a. The H-PCRF sends the updated QoS rules and event triggers to the V-PCRF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully.

4b. The V-PCRF may also perform further authorization of the rules based on local policies.

4c. The V-PCRF sends the updated QoS rules and event triggers to the BBERF using Diameter CCA.

5. The BBERF installs the received QoS Rules and event triggers. This may result in bearer binding being performed according to the rules. The BBERF also enables or disables service flow according to the flow status of the corresponding QoS Rules. The result of the QoS rule activation may trigger the BBERF to send an additional Diameter CCR as described above to the PCRF, for example, to indicate that QoS rule activation has failed.

4.4.2.2 Visited access cases

Figure 4.4.2.2.1: Gateway Control and QoS Rules Request for visited access

1. The BBERF is triggered to either report an event or obtain QoS rules or both for a gateway control session.

2. The BBERF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report event or request QoS rules.

3. The V-PCRF stores the information received in the Diameter CCR and derives updated QoS rules and event triggers according to local policies and roaming agreements.

When the report event is subscribed by H-PCRF, the steps 3a~3d are executed instead of step3:

3a. The V-PCRF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report event.

For case 2a, the information received in step 2 is send to H-PCRF at command level.

For case 2b, the CCR is send with the information provided at subsession level within the Subsession-Enforcement-Info AVP.

3b. The H-PCRF stores the received information in the Diameter CCR and derives event triggers.

3c. The H-PCRF sends the event triggers to the V-PCRF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully.

3d. The V-PCRF may also perform further authorization of the rules based on local policies.

4. The V-PCRF provisions the updated QoS rules and event triggers to the BBERF using Diameter CCA.