"PC_RENEWAL_DATE" Not Aligned With timezones/daylight savings (Doc ID 2757661.1)

Last updated on MARCH 08, 2021

Applies to:

Oracle Communications Network Charging and Control - Version 12.0.2.0.0 and later
Information in this document applies to any platform.

Symptoms

Whenever customer sets a timezone for a periodic charge and when Personal Computer (PC) moves from state 3(precharge0) -> 6(charge attempt that is renewal is happening) then PC_RENEWAL_DATE hour and minutes in Simple Objects Access Protocol*SOAP) request was adjusting according to the PC start date.

EXPECTED BEHAVIOR
-----------------------

Customer expects the PC_RENEWAL_DATE to be alligned with the PC configured timezone.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Have a subscription that started during daylight savings, and is currently renewing during non-daylight savings:

PC: 8496

START : 20200826023105

2. To start, current state 3 with the current expiry 24 hours prior to renewal:

STATE: 3 (Pre-charge 3)

EXPIRY : 20210325033146

BUCKETS: 20210326033146

3. Here, use VWARS_sysdate.cfg, trigger the renewal (expiry 20210325033200). The resulting SOAP message contains:

<ccs:ON_Parameter_Name>PC_RENEWAL_DATE</ccs:ON_Parameter_Name>

<ccs:ON_Parameter_Value>2021-03-26T02:31:05Z</ccs:ON_Parameter_Value>

The date value here is wrong. If it were aligned with the pending expiry of the PC, it should be 2021-03-26T03:31:05 (offset accordingly by the start date).

Now, it is in state 6, the expiry is when the PC will renew. The PC and buckets have the same expiry:

STATE: 6 (Active)

EXPIRY : 20210326033146

BUCKETS: 20210326033146

4. Again, use VWARS_sysdate.cfg trigger the renewal (expiry 20210326033200). The resulting SOAP message contains:

<ccs:ON_Parameter_Name>PC_RENEWAL_DATE</ccs:ON_Parameter_Name>

<ccs:ON_Parameter_Value>2021-03-26T04:31:46Z</ccs:ON_Parameter_Value>

The date value here is wrong again. It can either be aligned with the current expiry date of the PC, in which case it should be 2021-03-26T03:31:05, or aligned with the "next" expiry date of the PC, in which case it should be 2021-04-26T02:31:05. 04:31 is not correct!

After renewal, it is state 3 again, the PC is set to expire next during April - noting that the timezone has changed again and is back into the daylight savings:

STATE: 3 (Pre-charge 3)

EXPIRY : 20210425023146

BUCKETS: 20210426023146