DUCR Charges Do Not Round To The Next Billing Period
(Doc ID 2672753.1)
Last updated on MAY 29, 2020
Applies to:Oracle Communications Network Charging and Control - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC) 22.214.171.124.0 version,
The Billing Period affects the rounding of the charge. For a voice call using EDR Control Agent (ECA), if the Billing Period is configured as 60 seconds, the subscriber pay for each 60 second block. If the Subscriber talks for 30 seconds, they need to pay for 60 seconds block and if they talk for 61 seconds they need to pay for 120 seconds.
Consider a Data Session scenario via ECA, where the Billing Period is 51200 KB (50 MB). So if the subscriber consumes 60 MB, then they should be charged for 100 MB. But they are only charged for 50MB, if charged via a Direct Unit Charge Request (DUCR) node. Here the DURATION_CHARGED of a call is not adjusted correctly to the Billing Period.
The charging using DUCR should match a real-time charge for the same amount and charge correctly to the Billing Period.
The issue can be reproduced at will with the following steps:
1. On NCC 12.0,.2 Version, perform the interaction via ECA, which provides the IDP and ACR to populate the fields for the Direct Unit Charge(DUCR) node.
2. Use a Control Plan with an "Attempt Terminate to Pending with Duration"(ATPD) node and the DUCR Node with "Use Actual Duration" set.
3. Check whether the Duration is charged correctly as per the configured Billing Period.
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