The UDRs in PCRF.Rules store information about different rules regarding the provided quality of service for different subscribers.
See APL - PCC Runtime Support (3.1) for further information about how to use the PCC.Rules UDRs with APL.
...
| Object | Description |
|---|
Rules_Mapping | A flexible mapping table used to map from an external representation to a list of rules. The mapping should not include any information related to a specific subscriber. |
Rules | Rules contains the rule settings regarding quality of service and charging that should be applied for the subscribers. |
Overview of the Rules Data Model
The different UDRs within the Rules Data Model are connected as follows:
...
Overview of the Rules Data Model
RulesMapping UDR
In the RulesMapping UDR you set up the priority for the rules mapping, the product, enforcements, notifications, etc that the rules mapping should use and the PCC rules that should be applied.
...
| Info |
|---|
| title | Example RulesMapping UDR |
|---|
|
The following values: | Code Block |
|---|
ID=11
Priority=2
Arguments=['Product 1']
Targets=[1,2]
ID=12
Priority=1
Arguments=['Product 2-4']
Targets=[3]
StopFallthrough=yes |
will give the following setup: The second mapping table, with priority 1, will have higher priority than the first one, with priority 2. The first mapping table use the product Product 1, while the second mapping table use the products Product 2, Product 3, or Product 4. The first mapping table uses PCC Rules with IDs 1 and 2, while the second mapping object uses the rule with ID 3. If the second mapping table is active, only the rules for this table will be returned even if other rules apply.
|
PCC_Rule UDR
In the PCC_Rule UDR you determine the period during which the rule should be active, the charging rule that should be applied and the quality of service that should be applied for the rule.
Field | Description |
|---|
ID (int)
| The unique ID of the rule. |
Period (string)
| The activity period that the rule should have, see Periods Data Model Rules (3.1). |
Charging_Rules (list<Charging_Rule (PCRF.Rules)>))
| The charging rules that should be applied for this rule, see the section below, Charging_Rule UDR. |
Rule_Name (string)
| The name of the rule. |
QoS (QoS_Information (PCRF.Rules)
| The quality of service that should be applied for this rule, see the section below, QoS_Information UDR. |
...
| Info |
|---|
|
The following values: | Code Block |
|---|
ID=1
Period='WEEKDAYS'
Charging_Rules=[1]
Rule_Name='PRIMARY'
QoS=[20]
ID=2
Period='NIGHTS'
Charging_Rules=[3]
Rule_Name='SECONDARY'
QoS=[10]
ID=3
Period="WEEKENDS'
Charging_Rules=[5]
Rule_Name='THIRD'
QoS=[30] |
will give the following setup: The IDs used for the three rules; 1,2 3, are the IDs stated as Targets in the mapping tables, see the section above, RulesMapping UDR. The three rules are active during three different periods; WEEKDAYS, NIGHTS and WEEKENDS, see Periods Data Model Rules (3.1). Rule number 1 uses the charging rule with ID 1, rule number 2 uses charging rule with ID 3 and rule number 3 uses charging rule with ID 5, see the section below, Charging_Rule UDR. The names of the rules are PRIMARY, SECONDARY and THIRD. The first rule uses QoS ID 20, the second rule uses QoS ID 10 and the third rule uses QoS ID 30, see the section below, QoS_Information UDR.
|
Charging_Rule UDR
In the Charging_Rule UDR you determine the Static, Dynamic or Final Indication that should be used for the charging rule.
...
| Info |
|---|
| title | Example Charging_Rule UDR |
|---|
|
The following values: | Code Block |
|---|
ID=1
Name='PRIMARY'
Static_Rule=111
Dynamic_Rule=
Final_Indication_Rule=
ID=3
Name='SECONDARY'
Static_Rule=112
Dynamic_Rule=
Final_Indication_Rule=
ID=5
Name='REST'
Static_Rule=
Dynamic_Rule=
Final_Indication_Rule=200 |
will give the following setup: The first charging rule, with ID 1 and name Primary, uses the static rule with ID 111. The second charging rule, with ID 3 and name Secondary, uses the static rule with ID 112. The third charging rule, with ID 5 and name Rest, uses the final indication rule with ID 200.
|
The QoS_Information UDR contains Quality of Service parameters according to 3GPP specifications TS 29.212 and TS23.203.
...
| Info |
|---|
| title | Example QoS_Information UDR |
|---|
|
The following values: | Code Block |
|---|
ID=10
Name='Quality A'
APN_AGG_MBR_DL=32
APN_AGG_MBR_UL=32
GBR_DL=64
GBR_UL=64
MBR_DL=128
MBR_UL=64
QCI=7
ID=20
Name='Quality B'
APN_AGG_MBR_DL=32
APN_AGG_MBR_UL=32
GBR_DL=64
GBR_UL=64
MBR_DL=128
MBR_UL=128
QCI=4 |
will give the following setup: The maximum aggregated bit rate for both uploading and downloading data is 32 kbit/s for both QoS settings, Quality A and Quality B. The guaranteed bit rate for both uploading and downloading data is 64 kbit/s for both QoS settings. The maximum bit rate for uploading data is 64 kbit/s for Quality A and 128 kbit/s for Quality B. The maximum bit rate for downloading data is 128 kbit/s for both QoS settings. The first QoS setting uses Quality of Service Indicator 7, while the second uses Quality of Service Indicator 4.
|
Static_Rule UDR
Static rules are provisioned via the Gx interface and can be activated or deactivated at any time.
...
| Info |
|---|
| title | Example Static_Rule UDR |
|---|
|
The following values: | Code Block |
|---|
ID=111
Rule_Name='STATIC 1'
ID=112
Rule_Name='STATIC 2'
ID=113
Rule_Name='STATIC 3' |
will give the following setup: |
Dynamic_Rule UDR
Dynamic rules are dynamically provisioned via the Gx interface. Dynamic PCC rules can be installed, modified and removed at any time.
...
Below is a screenshot of the UDR Assistance displaying the Dynamic_Rule UDR:
Dynamic_Rule UDR
Final_Indication_Rule UDR
A Final Indication Rule is used to indicate when a subscriber should be redirected or blocked based on reaching a certain usage level. In the case of mobile data traffic control, this would be done by sending the information in the Gy-answer (as opposed to Gx, which is used for Static and Dynamic rules), in the Multiple-Services-Credit-Control field "Final-Unit-Indication", with the same fields populated as the fields in this table.
...
