High Availability Sy deployment using shared SLC database
(Doc ID 2427105.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In the current High Availability (HA) implementation, Service Logic Controller (SLC) servers rely on the connected network elements to manage the distribution of traffic between nodes. These can be on a load-share or active/standby configuration to one or several nodes.
Transactions started on one SLC node continue to be serviced by that node, that is the transaction data remains local to each SLC node and is not shared between the SLC nodes. In the event of either a planned or unplanned outage of an SLC node, all active transactions on that node are lost. New transactions would then be targeted to one of the other available SLC nodes.
Voice calls and data sessions have periodic commits, which further minimize the opportunity for revenue loss from a planned or unplanned outage of an SLC node. This is achieved since the revenue loss is limited to the amounts reserved but not committed which, through configuration, will be only part of a session and limited to the most recent reservation chunk within those sessions that remain active.
The Diameter SY (DSY) Interface acts as the Sy reference point between an external Policy and Charging Rule Function (PCRF) and the OCS (Prepaid Charging).
In case of Sy, if serving SLC goes down and request that arrive to next available SLC may not handle the already running DSY session since there is no shared SLC database between the nodes.
Using shared SLC database will help in overcoming the situation where if the serving SLC goes down then failover should takes place and already established DSY sessions should not drop. This can be achieved by making use of shared SLC database in high availability implementation. Below pictorial representation
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