Charging Support for HR Roaming
This section describes the charging support for the HR roaming feature.
This feature supports the following functionalities:
-
QBC charging.
-
Roaming QBC profiles configuration.
-
Relay roaming QBC profiles to the CHF.
-
Receive roaming QBC profiles from the CHF.
-
Relay roaming QBC profiles from the vSMF to hSMF.
-
hSMF relays roaming vSMF QBC profiles to hCHF.
-
vSMF relays roaming hSMF QBC profiles to vCHF.
-
In the vSMF, UPServ in collaboration with charging, creates PDRs for QFI on the N4 interface and associated corresponding URR, which are derived from the roaming QBC profile.
-
Relay URR usage reports derived from the QBC profile to the respective CHF in QFi containers, which are meant for QosFlow reporting.
-
Disable QBC for the sessions for which the corresponding QBC charging profiles could not be identified.
-
Support Fail-Open from the CHF.
-
Configuration to enable QBC on the hSMF, vSMF and non-roaming SMF.
Using the Roaming QBC Profile
The SMF determines the QBC profile based on the local interface. The QBC URR is created based on the limits present in the profile.
The following triggers are applicable for HR charging:
-
Triggers armed at Session Level
-
Reports the QBC in the session level URR.
-
Reports the QBC for the CC events.
-
-
Triggers armed at the QBC profile
-
Limits are used in QBC URRs.
-
Reports all the QBC URRs for an event armed at the QBC profile.
-
The following sample code shows the different triggers and their corresponding values.
Sess trigger []
Vol 100
time 100
RAT
Rg X trigger[]
Vol 10
time 10
PLMN
RoamignQbcprofile trigger[]
Vol 20
time 20
ULI
Sess URR
Vol 100
tim 100
RGX_URR
vol 10
tim 10
QBCURR1
Vol 20
tim 20
QBCURR2
Vol 20
tim 20
When RTA happens
Query all RG and all QBC urr
when PLMN change
Query RG X URR
when ULI changes
Query all QBC
Accounting Static or Predefined URR Usage to Session Level URR
In the previous release, the CHF driven session limits were controlled by the PCF, dynamic in nature and applicable for the online and offline charging service. As a result, all the dynamic URRs were reported when a session level URR was reported. Also, the offline URR associated with the static or predefined rules were reported when a separate URR was met.
In the current release, the reporting mechanism is streamlined on the N4 interface for the session limits to report the following URRs:
-
The online and offline URRs associated with dynamic rules.
-
The offline URR associated with static or predefined rules.
-
All the QBC URRs.
NOTES:
-
In this release, the SMF does not report the online static or predefined URRs when a session limit is met.
-
In this release, rulebase ECGDR configuration is not required to get the static or predefined accumulated report for offline services.
When QBC is enabled, the SMF associates SessLevelUrr to the default UL or DL PDR, which carries the rulebase name. The UPF associates this URR to every SDF PDR or URR for all the static predefined rules.
-
During setup, the Sess Urr is associated with the default PDR. If the SMF does not have input during the setup time for creating the Sess level URR and later post setup, the CHF sets limits. These URRs are not honored.
MaxChangeinCC, MaxDeferredUrr and OOO Config
MaxChangeinCC
The HR roaming feature supports reporting of the QBC usage data when Max CC is met.
The MaxCC value can be controlled at the config level apart from it coming from the CHF. The priority order of selecting the MaxCC values, are as follows:
-
The CHF armed MaxCC.
-
The ChargingProfile when it's associated to a session.
-
If a session is enabled for QBC charging, use QbcProfile .
MaxDeferredUrr
The local config is used to configure the MaxDeffered value present in Charging-Profile. This is extended to ChargingQbcProfile. The priority order of selecting, are as follows:
-
The ChargingProfile when it's associated to a session.
-
If a session is enabled for QBC charging, use QbcProfile .
The MaxDeferred count is met when the combined value of UUC and QFICOntainer crosses the configured threshold value.
OOO Config
The OOO config is referred from Charg-Profile, which is associated to a session.
If it's not associated to a session, then it's referred from the QBC profile on the condition that the QBC charging is enabled for the session.