My Oracle Support Banner

5G CHF CDR Generation Issues (Doc ID 2864100.1)

Last updated on FEBRUARY 20, 2024

Applies to:

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


On Oracle Communications Elastic Charging Engine (ECE) Version,  Cloud Native Deployment,

Following issues/fixes have been identified on 5G Charging Function (CHF) Call Detail Record (CDR) generation:
1. localRecordSequenceNumber should resets to 0 after crossing the Maximum Limit of 4294967295.

2. LocalSequenceNumber will be incrementing for each instance of Used unit container, currently this is against Rating Group (RG) and not against charging session.

3. recordSequenceNumber will be incrementing for each CDRs generated against session id. Currently this is hard coded as -1 as default value. Further CDR getting close due to terminate will only have default

4. For Multiple records in the same CDR file, comma separator is missing between 2 records and ArrayList is not present.

5. External Trigger details for certain CDRs is not populated, whereas causeOfRecordClosing is correctly mentioned.


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.