Extra 10 Bytes Added to GSU When USU Is Zero in Roaming Zones
(Doc ID 2914368.1)
Last updated on DECEMBER 12, 2022
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.4.7 Cloud Native Deployment, whenever a CCR-Update (CCR-U) Request having Uses-Service-Units (USU)=0 is received, ECE add extra 10 bytes to the next Granted-Service-Units (GSU). This issue is observed in roaming zones.
ACTUAL BEHAVIOR
------------------------
This is observed when setting the rateZeroQuantity parameter to "true" inside charging-settings.xml.
When this parameter is set to false then GSU calculation is working fine. But the user needs to set this parameter as "true" as per their business requirement.
EXPECTED BEHAVIOR
------------------------
ECE should not grant any extra bytes on the Granted Service Units after receiving a CCR-U with USU=0.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set rateZeroQuantity=true inside charging-settings.xml
2. Send CCR-I diameter usage request to ECE DiameterGateway for a sample account
3. Send CCR-Update request and see if ECE is responding with CCA-Update with GSU as expected
4. Send next CCR-Update request with USU=0 and check if ECE is responding with CCA having any extra bytes (example 10 bytes) added to the GSU
5. Send next CCR-Update request with USU=0 and check if ECE is responding with CCA having any extra bytes (example 10 bytes) added to the GSU
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 |
Cause |
Solution |
References |