Charge Period Precision In GUI Vs Database For Data Units
(Doc ID 2728153.1)
Last updated on NOVEMBER 19, 2020
Applies to:Oracle Communications Network Charging and Control - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Network Charging and Control (NCC) 220.127.116.11.0 version, the following charging scenario is given: a data session of 1100MB which should be charged at a price of 11 euros is charged with 10,99999 euros.
Charging in Network Charging and Control (NCC) is done as cost in smalls per unit:
- smalls precision is 1/100000 EURO
- unit size is 1KB.
- The cost per 50MB is 0.5 euro = 50000 smalls
As a per KB charge, this is 0.9765625 smalls per KB. NCC allows 6DP of entry in the Graphical User Interface (GUI), so 0.976562 has been entered - which creates a slight loss of precision.
The charge is calculated out on the wire:
1153433600 Bytes = 1126400KB for the "duration" that is charged: 1126400 * 0.976562 = 1099999.4368 = 1099999 smalls.
So part of a cent was lost here due to rounding.
As this is caused by the fact that "Charge(c/data unit)" field from "SMS GUI">"Services">"Prepaid Charging">"Rating Management">"Charge Periods"> "Edit Charge Period" window allows values with 6 decimal places, is it possible to enhance the SMS GUI so it will allow values with 7 decimal places?
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