6.5 Quality of Service Control rule
23.2033GPPPolicy and charging control architectureRelease 17TS
6.5.1 General
The Quality of Service control rule (QoS rule) comprises the information that is required to enable the user plane detection and the QoS control for a service data flow in the BBERF. The packets detected by applying the service data flow template of a QoS rule are designated a service data flow.
NOTE 1: The BBERF only supports service data flow templates consisting of a set of service data flow filters.
The PCRF shall ensure that each PCC rule in the PCEF has a corresponding active QoS rule in the BBERF. The QoS rule shall contain the same service data flow template, precedence and the QoS information as the corresponding PCC rule.
NOTE 2: During the course of a BBERF change procedure the BBERF might not be able to maintain the correspondence throughout the procedure. The post-condition for the procedure shall however be that corresponding PCC and QoS rules are active at the PCEF and BBERF.
There are defined procedures for activation, modification and deactivation of QoS rules (as described in clause 6.5.2). The PCRF may activate, modify and deactivate a QoS rule over the Gxx reference point.
The QoS rules are derived from the PCC rules.
Table 6.5 lists the information contained in a QoS rule, including the information name and whether the PCRF may modify this information in a QoS rule which is active in the BBERF. For the IE description, refer to clause 6.3.1. The Category field indicates if a certain piece of information is mandatory or not for the construction of a QoS rule, i.e. if it is possible to construct a QoS rule without it.
Table 6.5: The QoS rule information
|
Information name |
Category |
PCRF permitted to modify for an active QoS rule in the BBERF |
|
Rule identifier |
Mandatory |
No |
|
Service data flow detection |
||
|
Precedence |
Mandatory |
Yes |
|
Service data flow template |
Mandatory |
Yes |
|
QoS control |
||
|
QoS class identifier |
Mandatory |
Yes |
|
UL-maximum bitrate |
Conditional |
Yes |
|
DL-maximum bitrate |
Conditional |
Yes |
|
UL-guaranteed bitrate |
Conditional |
Yes |
|
DL-guaranteed bitrate |
Conditional |
Yes |
|
UL sharing indication |
No |
|
|
DL sharing indication |
No |
|
|
ARP |
Conditional (NOTE 3) |
Yes |
|
PS to CS session continuity |
Conditional |
No |
|
Access Network Information Reporting |
||
|
User Location Report |
Conditional |
Yes |
|
UE Timezone Report |
Conditional |
Yes |
|
NOTE 1: The Rule-Identifier uniquely defines an active QoS rule for a certain BBERF within the scope of a UE. NOTE 2: The QoS class identifier is scalar and accommodates the need for differentiating QoS in all types of IP‑CAN. The value range is expandable to accommodate operator specific policies. NOTE 3: If present in the corresponding PCC rule. |
||
6.5.2 Quality of Service control rule operations
QoS control rule operations consist of activation, modification and de-activation of QoS rules.
Activation of a dynamic QoS rule provides the QoS rule information to the BBERF via the Gxx reference point.
An active QoS rule means that:
– the service data flow template shall be used for service data flow detection;
– the service data flow template shall be used for mapping of downlink packets to the IP‑CAN bearer determined by the bearer binding;
– the service data flow template shall be used for service data flow detection of uplink packets on the IP‑CAN bearer determined by the bearer binding;
– QoS procedures associated with the QoS rule, if any, shall be invoked.
The PCRF may, at any time, modify an active QoS rule.
The PCRF may, at any time, deactivate an active QoS rule in the BBERF via the Gxx reference point. At IP‑CAN bearer termination all active QoS rules on that bearer are deactivated without explicit instructions from the PCRF to do so.