Spending Limit Control

Spending limit control is managed by the Nchf_SpendingLimitControl service (N28) which enables the Network Function (NF) to retrieve policy counter status information from the Charging Function (CHF).

The Nchf_SpendingLimitControl service is part of the CHF which communicates with the PCF. For more information about N28 and N40 communication and 5G Message flows, see MATRIXX 5G Integration.

Re-Evaluating Spending Limit Control Sessions

For Nchf_SpendingLimitControl, when re-evaluating policy and no policy counter is selected, the session is set to an invalid state and is not re-evaluated again. A Subscription Termination Request (STR) is sent. The NF service consumer should reply with a 204 No Content response. The Charging Server receives a Subscription Termination Response and deletes the policy session. If the Charging Server does not receive a response, it resends the STR up to the configured maximum number of times, with a configured delay between each retry. When the max retries has been exhausted, the session is deleted.

To configure the number of retry attempts, answer the following create_config.info question: Global:Session:Policy:Notify:How many attempts?. The default is 1.

To configure the delay between attempts, answer the following create_config.info question: Global:Session:Policy:Notify:How long (in seconds) to wait after each attempt?. The default is 30 seconds.