My Oracle Support Banner

CHF CDRs Not Updating Current User Location, RATType & UETimezone Under PDUSessionCharging (Doc ID 2994546.1)

Last updated on DECEMBER 22, 2023

Applies to:

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


It was found that whenever RAT changes or user location changes (along with some other immediate trigger) the first CDR that closes on CHF does not have latest user location under pDUSessionChargingInformation while on N40 interface traffic SMF is sending the latest user location info under pDUSessionChargingInformation.
While second CDR onwards the latest locations are updated in the CDRs and CDR data aligns with n40 traffic details.

As per legal compliance guidelines every CDR should have the latest location where user is located right now. And per 3GPP spec TS 132 255 this is description of user location info field under pDUSessionChargingInformation.


RAT - Radio Access Technology

CDR - Call Detail Record

CHF - Charging Function

SMF - Session Management Function

N40: Reference point between SMF and the CHF.

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.