How it Works
The QGR feature performs flow status and bandwidth limiting under the charging-action configuration. UPF applies the static configuration for QGR using RCM.
When a packet matches a ruledef, UPF performs a QGR match to check if a QGR is present with the matched ruledef or group. UPF returns the highest priority QGR.
-
If a QGR matches, UPF applies flow-action enforcement at charging-action, and then at QGR if charging-action allows the packet. If the packet drops, UPF skips the QGR-level flow-action enforcement.
-
If flow-action at QGR allows the packet, UPF enforces the QoS Enforcement Rule (QER) limiting on a packet. If the packet drops at QGR, UPF skips QER limiting.
-
UPF performs QER limiting at charging-action and then at QGR if the packet is allowed at charging-action.
UPF supports QoS-group-of-ruledefs configuration under the ACS service.
The following is a sample QGR configuration under ACS:
configure
active-charging service acs
qos-group-of-ruledefs QGR1
add-group-of-ruledef group
add-ruledef http
#exit
rulebase test
action priority 2 ruledef http charging-action standard
action priority 5 ruledef catchall charging-action standard
route priority 1 ruledef http-rule analyzer http
end
The following configuration is an example of QoS Group "QGR1" received over PCRF:
-qos-group-rule-install
--qgr-name QGR1
--qgr-mon-key 1
--qgr-flow-status 2
--qgr-precedence 1
--qgr-eqos-information
--qgr-eqos-mbr 1000 2000
--qgr-eqos-mbr-burst-size 1000 2000
--qgr-eqos-mbr-limit-conform-action 0 -1 0 -1
--qgr-eqos-mbr-limit-exceed-action 1 -1 1 -1
IE Support
UPF pushes the QGR in Session Establishment Request or Session Modification Request using the private IE—QGR-INFO-LIST. If there are changes to the QGR dynamic parameters, UPF triggers an Update FAR or QER. UPF sends the updated value in Session Establishment Request or Session Modification Request.
Currently, UPF does not support the monitoring-key parameter in QGR. Hence, UPF does not send URR associated with QGR in Session Establishment Request or Session Modification Request.
The following is the name and format of the private IE:
QGR-INFO-LIST:
Value:
Number of QGRs: 2
QGR INFO:
NAME: qgr-gor
PRECEDENCE: 3
OPERATION: QGR ADD
FAR ID: 0x8005
QER ID: 0x0004
QGR INFO:
NAME: qgr2
PRECEDENCE: 9
OPERATION: QGR ADD
FAR ID: 0x8006
QER ID: 0x0005
The following table describes the FAR format:
FAR ID |
Unique ID |
---|---|
Apply Action |
Flow-action defined in QGR. |
Extended Apply Action |
Private IE to communicate to QGR FAR. This IE includes Flow-Action—Discard Uplink, Discard Downlink, and Terminate Flow. |
Forwarding Parameters |
Contains the destination interface and redirect information if any. |
The following table describes the QER format:
QER ID |
Unique ID |
---|---|
Maximum Bitrate |
The maximum bit rate of QGR in Kbps.
|
Burst Size |
Private IE to configure the burst size.
|
Conform Action |
Private IE to configure the conform action.
|
Exceed Action |
Private IE to configure the exceed action.
|
Use the show subscribers user-plane-only callid call_id { far | qer } full all command to view the FAR and QER values.