Latency In Single CUG Support Without Having CUG Indentifier In Online Charging ( Diameter Ccr )
(Doc ID 1278890.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
There is a need to provide the CUG to subscriber. Normally CUG ( Closed User Group ) functionality is supported by Network and Billing used to get an identifier for CUG call to apply CUG rate. In this case customer wants to use CUG but network is not supporting it. So ERA (i.e the feature of Oracle BRM to support CUG) is used and it is for 100% prepaid (Online charging scenario).
Please share the benchmark results for friends and family (F & F) CUG, as customer need to know how latency will be affected if CUG is handled in BRM.
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