5G CHF || ECE Httpgateway || CDRs Violate 3gpp For Param Record Sequence Number
(Doc ID 2930589.1)
Last updated on FEBRUARY 28, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.8 version, Httpgateway
As specified in 3GPP TS 32.298, in "table 22.214.171.124.1: CHF record (CHF-CDR)", Record Sequence Number is a Conditional field that should only be there for partial records: "Partial record sequence number, only present in case of partial records.". So this field should only have a positive value since "The Record Sequence Number starts from one (1)"
Currently this values is populated as -1 for complete records.
NOTE: There are no functionality challenges here. This change is more aligned towards 3gpp compliance
This field should only have a positive value since "The Record Sequence Number starts from one (1)"
The issue can be reproduced at will with the following steps:
1. Create charging request.
2. Updated charging request and release request. Basically, any charging requests which trigger a closed cdr is sufficient to reproduce issue.
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