Redundant Database Subscriber Lookups in NCC/OC3C Convergent Charging Deployments
Last updated on DECEMBER 21, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), when deployed as a Convergent Charging solution (with a non-NCC Voucher Wallet Server (VWS)) which does not store subscriber information, a redundant subscriber database lookup is still being performed by the Service Logic Controllers (SLCs) for every request which triggers to the platform.
This unnecessarily adds latency to the overall request, additional CPU usage, and additional database resource usage for a query which will always return no information (because there is no subscriber information on the platform).
Installation of new OC3C/NCC software as a Convergent Charging solution.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms