5G CHF || ECE Is Unable To Identify The Duplicate Charging Requests (Doc ID 2980736.1)

Last updated on NOVEMBER 09, 2023

Applies to:

Symptoms

One could see that the same charging request is getting triggered.

Expected Behavior: Same charging request supposed to be identified as duplicate.

Actual Behavior : Duplicate charging request is getting processed and Allowance is getting impacted.

As per RFC 4006 - To ensure that the end user's account is not debited or credited multiple times for the same service event, only one place in the credit-control system should perform duplicate detection. Duplicates or out of sequence messages can be detected in the credit-control server based on the credit-control server session state machine (section 7), Session-Id AVP, and CC-Request-Number AVP. Implementations supporting the credit-control session failover MUST also ensure proper detection of duplicate or out of sequence messages. Currently it is a deviation from spec and a compliance issue.

Cause

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