Corrupt Timestamps Passed from ACS to BRM Through BCD

(Doc ID 2339960.1)

Last updated on DECEMBER 18, 2017

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C) that ship the Billing and Revenue Management (BRM) Charging Driver (BCD), an issue exists when trying to pass a date/time value from Advanced Control Services (ACS) to BRM through BCD.

When using date/time stamps in an ACS Control Plan, the date/time value is initially in epoch as an INTEGER:

2017/11/17 01:18:41    acsProfileDateStore.cc   576 [9555]        acsMacroNodes    extendedDate  : 1510881521
2017/11/17 01:18:41    acsProfileDateStore.cc   577 [9555]        acsMacroNodes    Converted     : Fri Nov 17 01:18:41 2017

However when it is forwarded to BCD (and thus BRM), it has become a completely different value:

2017/11/17 01:18:42           BcdSleeEvent.cc   145 [9555]     BCD_bcdSleeEvent      2         10103                TSTAMP [0] (825569584) Thu Feb 29 04:53:04 1996

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms