My Oracle Support Banner

CDR Failover - Identification Of Duplicate Detection And Adapting To Custom Field (Doc ID 2969095.1)

Last updated on AUGUST 23, 2023

Applies to:

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


Customer has 2 requirements:

1. Identification of duplicate detection
For cases of re-transmission of N40 requests, SMF (Session Management Function) sets re-transmission flag in N40 request payload. But this is not reflected in CDR (Call Detail Record). For some re-transmission cases, there is a probability CHF (Charging Function) stores CDR data successfully to DB (Database) but SMF unable to receive success from CHF. There should be some mechanism to identify such failover and re-transmission scenarios to avoid duplicate accounting of usage.

N40: Reference point between SMF and the CHF.

2. Adapting to custom field
Currently failover scenario is reflected in CDR using field Cause of Rec Closure which is a 3GPP field. Requirement is not to use 3GPP field for such scenarios instead use a vendor specific field in CDR.

3GPP = 3rd Generation Partnership Project





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.