Delayed SNR Generation Leading To Lower QOS
(Doc ID 3063520.1)
Last updated on DECEMBER 16, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Symptoms
On ECE 12.0.0.8.9 version, Diameter Gateway
ACTUAL BEHAVIOR
---------------
User encountering an issue where the SNR is being generated when an addon is set to expire within the next two hours.( their Validity-Time =7200)
This is causing issues for customers, as the SNR is sometimes triggered two hours after the addon has expired. During this period, if the customer purchases another addon, they are still being downgraded to a lower QoS tier. The issue seems to stem from a delay in the SNR generation before the addon expires.
Below are the 2 Issues observed here:
Issue 1: Consider If the 1st Addon is expiring at 17:04:18, and for the Gy updates after 15:04:18, for every Gy update, they are receiving the same SNR which it triggered during the time of purchase of the first addon
Issue 2 : After the expiry of the above addon, customer is purchasing same addon when the session is still active and for the next Gy Update, they are receiving the old SNR for the 1st Addon purchase
EXPECTED BEHAVIOR
-----------------------
There should not be any SNR getting triggered only because the addon is getting expired in next two hours.
Also if customer is purchasing same addon when the session is still active, for the next Gy Update, they should not receiver the old SNR for the 1st Addon purchase
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Purchase Addon with validity of around 2hour 10min (say at start time :Oct 1, 14:54:20 and end time : Oct 01 ,17:04:18)
2. Initiate Gx, Sy and Gy Sessions(at Oct 01, 15:01:27)
3. Send gy update-1 at Oct 01, 15:02:58
4. Send gy update -2 at Oct 01, 15:06:38 --> at this time the SNR is getting generated
5. Wait for Addon to expire at Oct 01 ,17:04:18 (same session is still active)
6. Purchase the same addon with validity end time as Oct 1, 20:10:00 (same session is still active -- test_gy_01102024_001 ) --> SNR generated wiht High Qos with Pending-Policy-Counter-Change-Time (2906,VM,v=10415,l=16) = 3936758659 (Tue Oct 01 20:10:00 JST 2024)
7. Gy Update at 17:15:10 --> This generates the old SNR as below , which makes the customer to go on Low QoS because of the pending-policy-counter-change-time
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |