Quota-Holding-Time (QHT) Should Not Be Reported When Granted-Service-Unit (GSU) Is Not Set
(Doc ID 2796338.1)
Last updated on AUGUST 11, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On performing an online usage update request, when the data bucket is completely consumed QHT is getting reported when GSU is not set.
During data breach, one can see that GSU is not set but QHT is getting reported in Credit Control Request (CCR).
QHT should not be reported when GSU is not set.
1. Place a mobile order for suppose 6GB promotion.
2. Consume data till 200MB is left.
3. Initiate a session and pass 181 MB. (GSU-19MB)
4. Pass 10MB as next update in the same session. (GSU - 9MB)
5. Pass 9MB as final update in the same session. (No GSU reported but could see QHT)
6. Terminated the session.
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