On configuring active charging service parameters, the session controller task pushes the modified parameters to all the session managers. The session managers are now informed of certain specific configuration changes that are supported as part of this feature. On detecting those specific configuration changes, a five-minute timer is started (if not already running) at each session manager.
At the expiry of the timer, if no additional changes were done to any of the active charging service parameters during this interval, all subscribers are updated with the information that there has been a configuration change. Transactional Rule Matching (TRM) is be re-engaged for all flows (eligible for TRM) when data is received for that subscriber session.
At the expiry of the timer, if there had been additional configuration changes, the timer is restarted. This continues for two iterations, after which all the subscribers are updated with the information that there has been a configuration change and there is a need to re-engage TRM.
This feature does not impact subscriber flows that are not under the purview of TRM.
Transactional Rule Matching (TRM) is re-engaged only in the following scenarios:
Rule Base Configuration
Host Pool Configuration
Addition of new Charging Action if charging action is referenced in rulebase
In addition, restrictions are added to prevent ruledef, group-of-ruledefs, charging action, and host pool deletion if these configurations are being referenced within any rulebase. For example, an action priority line containing a particular ruledef is deleted before deleting the ruledef configuration. Deleting an action priority line results in TRM being re-engaged for affected subscribers based on the existing behavior.