My Oracle Support Banner

Queries Regarding CHF NfStatus in a 5G Setup (Doc ID 2960440.1)

Last updated on AUGUST 21, 2023

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


Information regarding Charging Function (CHF) Integrations with Network Repository Function (NRF):

Qn1. nrfHeartBeatRetryCount is used to enter the number of retries if Registration Fails. It is expected that status of CHF will change from Registered to Suspended after all the retries failed. After how long will the CHF become UNDISCOVERABLE after Suspended? Is there a mechanism to bring Suspended CHF back to Registered State automatically?

Qn2. If CHF fails to register with one NRF, but succeeds to register with other NRF, then what will be the state of CHF? (Assuming it to be Registered)

Qn3. What will be the behavior of HTTPGateway when it receives a Nchf_ConvergedCharging or Nch_SpendingLimitControl Request and simultaneously its status is changed to Suspended (Probably because of NRF failure)?
Qn4. What is the behavior of CHF if it receives Error in a Heart Beat Response? For example, it receives a response from NRF but 503 error in response - could be for any reason.
The retry mechanism for timeout is the same as for Error? Is there a way to differentiate these two Retry Mechanisms?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.