Late Bucket Expiry
(Doc ID 2771133.1)
Last updated on APRIL 21, 2023
Applies to:Oracle Communications Network Charging and Control - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Customer have a late bucket expiry, followings are the sequence of events:
1) On the 5th of Jan, the Periodic Charge(PC) pre-charge change happens, bucket goes from 3-6 [expiry 24 hours later] and generates the pending renewal Recharge Real Time Wallet Notifications (RTWN). This process triggers a sentinel bucket set to expire immediately - this is attached to a different RTWN that is set up for friendly hours.
--> This new bucket is created [Event Detail Record(EDR)] but does not expire straight away.
2) On the 6th of Jan, the PC renewal happens, bucket goes from 6-3 [expiry 1 month - 24 hours] and generates the renewal RTWN.
--> The new bucket from the previous transition still has not expired.
3) Between the 5th->14th of Jan the subscriber is using data, making calls - lots of account activity
--> The new bucket has still not expired
4) On the 14th Jan, customer performs a friendly user migration - which involves stopping the Service Logic Execution Environment (SLEE) across the entire platform.
5) After services are restarted, the bucket from point #1 finally expires. This results in an erroneous RTWN being sent to the subscriber stating that their PC is going to renew in 24 hours, when in reality it already renewed almost a week ago.
Checking the Voucher and Wallet Server (VWS), there are no errors or messages that seem to indicate that the expiry plugin is having difficulties. Other subscribers using this same process with the same sentinel bucket don't seem to be facing the same issue. How to resolve this 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